vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 (edited) 1 minute ago, crusher11 said: The same as https://domain:443. "This site can't be reached. [IP] refused to connect. ERR_CONNECTION_REFUSED" and https://localip:8920 Edited July 11, 2021 by vdatanet
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 ERR_CONNECTION_REFUSED smells like problems with the certificate. Are you sure the certificate is correct? Issue with SSL cert causing Server to refuse connections. - General/Windows - Emby Community HOWTO: Use custom SSL cert and keep private key secure - General/Windows - Emby Community
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 46 minutes ago, vdatanet said: ERR_CONNECTION_REFUSED smells like problems with the certificate. Are you sure the certificate is correct? Issue with SSL cert causing Server to refuse connections. - General/Windows - Emby Community HOWTO: Use custom SSL cert and keep private key secure - General/Windows - Emby Community Cloudflare is on 'flexible' and Emby is on 'disabled', which was supposed to take the certificate (which has worked fine until the new router, BTW) out of the loop. What use would a server log be? We can't connect to it, so there wouldn't be anything to log would there?
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 9 minutes ago, crusher11 said: Cloudflare is on 'flexible' and Emby is on 'disabled', which was supposed to take the certificate (which has worked fine until the new router, BTW) out of the loop. What use would a server log be? We can't connect to it, so there wouldn't be anything to log would there? To see it's there an error like this: Quote Error HttpServer: Exception loading certificate Now forget cloudflare and set connection ssl mode to prefered
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 Just now, vdatanet said: which has worked fine until the new router, BTW Neither you nor I know how the old router was set up, so we're starting from scratch.
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 The goals should be: 1. First run it without cloudflare 2. Then configure cloudflare 3. Finally nginx
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 8 minutes ago, vdatanet said: To see it's there an error like this: Now forget cloudflare and set connection ssl mode to prefered I did a Ctrl+F for "certificate" and "error httpserver", nothing.
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 Just now, crusher11 said: I did a Ctrl+F for "certificate" and "error httpserver", nothing. Well, you had ssl mode disabled. Set Emby's ssl mode to preferred
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 7 minutes ago, vdatanet said: Well, you had ssl mode disabled. Set Emby's ssl mode to preferred No change.
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 8 minutes ago, crusher11 said: No change. Is this the correct certificate for your custom domain?
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 9 minutes ago, vdatanet said: Is this the correct certificate for your custom domain? It is not. I changed it. It changed itself back.
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 (edited) Apparently the server needs a reboot to make that stick. Now localip:8920 gives me a "page isn't working, [ip] didn't send any data, ERR_EMPTY_RESPONSE" error. Same result from remoteip:443 Edited July 11, 2021 by crusher11
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 (edited) 9 minutes ago, crusher11 said: Apparently the server needs a reboot to make that stick. Now localip:8920 gives me a "page isn't working, [ip] didn't send any data, ERR_EMPTY_RESPONSE" error. Same result from remoteip:443 So, you don't have the pfx certificate? My configuration is different, I have a purchased certificate, first I used it in Emby and then I configured nginx to use it and I have emby secure connections disabled. Nginx connects to Emby using non ssl: proxy_pass http://127.0.0.1:8096; # Local emby ip and non SSL port Edited July 11, 2021 by vdatanet
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 46 minutes ago, vdatanet said: So, you don't have the pfx certificate? I do, it was just pointed at the wrong folder. I had everything in /volume1/Emby, but then Emby changed its folder structure and took /volume1/Emby for its own files so I moved everything to /volume1/Emby Libraries, and just forgot to update the link to the SSL certificate. Now that it's pointing to the correct place, I get the empty response error.
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 4 minutes ago, crusher11 said: I do, it was just pointed at the wrong folder. I had everything in /volume1/Emby, but then Emby changed its folder structure and took /volume1/Emby for its own files so I moved everything to /volume1/Emby Libraries, and just forgot to update the link to the SSL certificate. Now that it's pointing to the correct place, I get the empty response error. Did you check the server log after changing this?
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 40 minutes ago, vdatanet said: Did you check the server log after changing this? Still nothing for 'certificate' or 'error httpserver'.
vdatanet 1617 Posted July 11, 2021 Posted July 11, 2021 Look for this in the server log Error App: Error loading cert How did you generate the certificate? Is the password correct?
crusher11 1101 Posted July 11, 2021 Author Posted July 11, 2021 36 minutes ago, vdatanet said: Look for this in the server log Error App: Error loading cert How did you generate the certificate? Is the password correct? No sign of that error. I generated the certificate through CloudFlare. I assume the password is right; it was working previously and I haven't changed it.
Q-Droid 989 Posted July 11, 2021 Posted July 11, 2021 (edited) I commend the people trying to help, you are all very patient. If everyone agrees can the last six pages of this thread get split into a separate one? All of the "troubleshooting" is junking up this How To. Edit: @Happy2Play? Edited July 11, 2021 by Q-Droid 4
Happy2Play 9780 Posted July 11, 2021 Posted July 11, 2021 Split topic @crusher11 please follow this topic.
vdatanet 1617 Posted July 12, 2021 Posted July 12, 2021 3 hours ago, crusher11 said: @rodainas @vdatanet I'm out of ideas, let's see if anyone else can contribute something more.
crusher11 1101 Posted July 12, 2021 Author Posted July 12, 2021 (edited) 3 minutes ago, vdatanet said: I'm out of ideas, let's see if anyone else can contribute something more. Well FWIW http://domain and https://domain both work, although the latter warns that it's not secure. Edited July 12, 2021 by crusher11
vdatanet 1617 Posted July 12, 2021 Posted July 12, 2021 (edited) 12 minutes ago, crusher11 said: Well FWIW http://domain and https://domain both work, although the latter warns that it's not secure. Well, that’s progress. If you click on the browser security lock, what information does the ssl certificate give you? Edited July 12, 2021 by vdatanet
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now