SSL issues #725
Replies: 12 comments 3 replies
-
Navino16 wrote at Nov 29 2017 13:51:21 UTC: Hello, Same issue for me |
Beta Was this translation helpful? Give feedback.
-
rockhearted wrote at Nov 29 2017 13:51:21 UTC: LordRalex could you please look into this? |
Beta Was this translation helpful? Give feedback.
-
LordRalex wrote at Nov 29 2017 13:51:21 UTC: HTTPS with 1.1.4 has a known issue with actually determining if it is using https. https://github.com/PufferPanel/PufferPanel/blob/master/src/core/daemon.php#L229 Any place in this function where it says Request::head needs to be changed to Request::get |
Beta Was this translation helpful? Give feedback.
-
rockhearted wrote at Nov 29 2017 13:51:21 UTC: LordRalex Any reason why is it not fixed in the repo even though you know the solution? |
Beta Was this translation helpful? Give feedback.
-
Navino16 wrote at Nov 29 2017 13:51:21 UTC: And when can we have official 1.2 ? |
Beta Was this translation helpful? Give feedback.
-
rockhearted wrote at Nov 29 2017 13:51:21 UTC: LordRalex but it says that "This update has already been run Are you sure you wish to run the update anyway? [y/N]: " |
Beta Was this translation helpful? Give feedback.
-
rockhearted wrote at Nov 29 2017 13:51:21 UTC: I fixed this by switching back to http from https. To do this, I removed the https config from my nginx configuration, and removed the https.key and .pem file from /etc/pufferd as well. After that, restart nginx and pufferd daemon both. |
Beta Was this translation helpful? Give feedback.
-
puffrfish wrote at Nov 29 2017 13:51:21 UTC: PufferPanel and pufferd v1.2 have been released https://community.pufferpanel.com/topic/718/pufferpanel-v1-2-pufferd-v1-2-docker-and-pufferd-packages |
Beta Was this translation helpful? Give feedback.
-
specialkk wrote at Nov 29 2017 13:51:21 UTC: This still seems broken for me in 1.2. I believe I have everything set up as outlined with
and checking |
Beta Was this translation helpful? Give feedback.
-
specialkk wrote at Nov 29 2017 13:51:21 UTC: The thread here solved my issue. I had to set the internal IP of the node to the FQDN so that my SSL certificate would verify. It would be nice to have the ability to disable host verification for requests to local nodes though since otherwise I have to edit my |
Beta Was this translation helpful? Give feedback.
-
Navino16 wrote at Nov 29 2017 13:51:21 UTC: specialkk I have the same issue as you. I already set the FQND but not working. What have you change in you /etc/hosts ? |
Beta Was this translation helpful? Give feedback.
-
specialkk wrote at Nov 29 2017 13:51:21 UTC: Navino16 Sorry I disappeared! The router on the network I'm hosting doesn't support loopback, so I had to add entries in
Just don't be confused by the If your router supports static routes, you should prefer to set the mapping from the FQDN to your internal IP there. |
Beta Was this translation helpful? Give feedback.
-
rockhearted wrote at Nov 29 2017 13:51:21 UTC:
I'm getting this error in my browser:
Unable to connect to web socket server, will attempt to use timed refresh
In
service pufferd status
, I'm getting multiple errors like this:pufferd[4333]: http: TLS handshake error from 127.0.0.1:34872: tls: first record does not look like a TLS handshake
Through some digging in the forums I found that its because my pufferd is not being contacted using https
My etc/pufferd has the certbot generated fullchain.pem and privkey.pem renamed as mentioned here https://www.pufferpanel.com/docs/using-letsencrypt-with-pufferpanel with 600 permissions.
I also tried renaming my public IP for that node to the one specified for the letsencrypt domain. Also tried removing and adding back the private IP 127.0.0.1.
Also tried changing the authserver and infoserver to https but that made the panel slow and didn't fix the problem, so I changed it back to http.
Any ideas why pufferd won't communicate over https?
Edit- Do I need to change anything here(in config.json)?
"web": "0.0.0.0:5656",
"sftp": "0.0.0.0:5657"
or mark
forward
totrue
? What does that even do?Beta Was this translation helpful? Give feedback.
All reactions