It might work if you used “https://” since its encrypted.
However, I’m getting the impression that whether you put the “https://”, or a port on your base_url, or whether you have a base_url entry at all, impacts other things like whether you need port forwarding on your router, which ports you might need to forward, etc. So, since you have it working, DON’T TOUCH IT! 
. I’m planning to investigate all these nuances when I get extra time.
At least you know it wasn’t errors you were making!
I’ve read if you leave “https://” and any port off your base_url setting in configuration.yaml it defaults to port 443. However, if you specify port, you may be able to forward 8123 external to 8123 internal… maybe there’s another option for you?
Check out the first comment after this blog post:
Same here… ever find a solution?
Yes indeed I found, I figured out that my internet had two routers and the both had wifi, and they were fighting in some way to give dinamic ip´s for all my devices, even though I have had fixed all my device´s ip before. So I disconnected one of them, transfer all my devices to the modem + router, then I was able to set a fix IP with no problems. After this I opened some port like 9000/9150 to 443 and 443 to 8123, somehow this time it works right away. I don´t even know if it´d had worked whithout any port forwarding but just in case I left open.But let me know where you are stucked so I´ll try to help you.
Figured it out.
No more need for let’s encrypt so I uninstalled that add-on. Forwarded the ports accordingly, changed the “accept_terms” to true, added proper entries to configuration.yaml.
good to go!
Thanks tho!
Would you mind elaborating on the “forwarded the ports accordingly”?
Thanks
Did you figure it out?If I remember correctly I needed to comment out hue because it was using port 80, then start the setup process. Then I just followed the directions.