I can't communicate with the daemon pufferd when using HTTPS #610
Locked
LordRalex
announced in
Legacy - Support
Replies: 1 comment 1 reply
-
GoadingGoat wrote at May 25 2017 12:46:25 UTC: I also had issues with my ssl configuration initially, but i can assure you there are no major bugs as mine works with ssl. I suspect your problem is that you need to update the nodes public ip to the domain name you used for your ssl certs. seeing as it is trying to connect to the node using 127.0.0.1 still |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
unixfox wrote at May 25 2017 12:46:25 UTC:
Hello,
I'm receiving an error when I try to start, install, stop a server on the server panel. According to the console of my web browser it's a 502 (so an internal server error). Everything is working fine on http.
I correctly set up the SSL for pufferd using the Let's Encrypt certificates:
Here is the logs from pufferpanel:
And from pufferd:
Did I made a mistake or is this a bug?
Beta Was this translation helpful? Give feedback.
All reactions