-
Notifications
You must be signed in to change notification settings - Fork 407
Description
There's a very nasty bug I'm encountering when trying to run BTC Pay Server on a server that already has port 80 and 443 in use - therefore I attempted to install on different ports.
The issue is that the HTTP url is totally fine and accessible however it's crippled for configuration purposes like creating an account etc since it is not encrypted and displays the warning on the web UI front page when you try to create / login.
I've tried looking at the tickets but couldn't find anything that helped. I really suspect this a bug that is easily reproducable by simply running it on a different port other than 80 and 443.
I've used the command to entirely remove btcpay server and went back through the steps with the same results - absolutely reproducible from what I am seeing.
The reason this is somewhat critical is that a lot of people already spend money on their servers for webservers and to spend even $10 per month on another VM just to run BTC Pay seems a bit wasteful when you're thinking about essentially spending $120 USD per year for a small but critical bug that could be fixed.
I hope someone is able to resolve this soon