NGINX - troubleshooting

[crusher11 1100]

2 minutes ago, rodainas said:

Whats the error for 4343?

This site can’t be reached

[domain] refused to connect.

[rodainas 191]

Just now, crusher11 said:

This site can’t be reached

[domain] refused to connect.

Check your cloudfare ssl encryption level please

Select flexible

 

[vdatanet 1617]

Is this cert correct?

 

[rodainas 191]

Just now, vdatanet said:

Is this cert correct?

 

Lets do the test ignoring that cert for now.

[vdatanet 1617]

1 minute ago, crusher11 said:

This site can’t be reached

[domain] refused to connect.

And:

https://publicip:4343

[vdatanet 1617]

13 minutes ago, vdatanet said:

Test this:

Set Emby's public ports to 80 and 443

Set router forwading 80 to 8096 and 443 to 8920

Have you tried this? I think it's easier to use standard ports.

[rodainas 191]

He can try that but the problem with the second port is certificate related, changing to that will avoid the use of domain:port on the url but the error will persit on https (via 443).

Edited July 11, 2021 by rodainas

[rodainas 191]

I have to go so here are some ideas to try them after.

Ok if setting the cloudfare encryption to flexible, and accessing https://yourdomain.com:4343 works.

If after that you want to have encryption level to full or strict you need to generate a new proper certificate on your machine, after getting the certificate and properly pointing to it on emby network settings, set your external domain there too (example: mydomain.com , dont use https:// there just the domain you are using to access it).

When thats set correctly, then you can go back to cloudfare and try the encryption level to full and/or strict (strict if you are generating it with a certificate authority like letsencrypt)

If you dont want to use domainname:port, do as vdatanet says and change your emby public ports to 80 and 443, and change your router forwarding to that. If thats is set correctly, you can access your server via http://domainname.com or https://domainname.com

Edited July 11, 2021 by rodainas

[crusher11 1100]

32 minutes ago, rodainas said:

Check your cloudfare ssl encryption level please

Select flexible

 

It's currently set to Full.

[rodainas 191]

I know is set to full, that why is not working.

[rodainas 191]

11 minutes ago, rodainas said:

I have to go so here are some ideas to try them after.

Ok if setting the cloudfare encryption to flexible, and accessing https://yourdomain.com:4343 works.

If after that you want to have encryption level to full or strict you need to generate a new proper certificate on your machine, after getting the certificate and properly pointing to it on emby network settings, set your external domain there too (example: mydomain.com , dont use https:// there just the domain you are using to access it).

When thats set correctly, then you can go back to cloudfare and try the encryption level to full and/or strict (strict if you are generating it with a certificate authority like letsencrypt)

If you dont want to use domainname:port, do as vdatanet says and change your emby public ports to 80 and 443, and change your router forwarding to that. If thats is set correctly, you can access your server via http://domainname.com or https://domainname.com

As said here, if flexible works for you, then the problem is as I suspect the certificate you have set on emby machine, if you want to use full you need to generate a new valid certificate simple as that.

Edited July 11, 2021 by rodainas

[crusher11 1100]

10 minutes ago, rodainas said:

As said here, if flexible works for you, then the problem is as I suspect the certificate you have set on emby machine, if you want to use full you need to generate a new valid certificate simple as that.

Flexible also fails.

[rodainas 191]

Add the domain to emby netwok settings just domainname.com and ssl settings to preferred if that doesnt work use disabled.

[crusher11 1100]

The domain was already added.

It's refusing to connect, it's not giving a certificate error. Changing SSL settings in Emby doesn't fix it either.

 

[vdatanet 1617]

4 minutes ago, crusher11 said:

The domain was already added.

It's refusing to connect, it's not giving a certificate error. Changing SSL settings in Emby doesn't fix it either.

 

Did you try using default ports? 80 and 443

[crusher11 1100]

1 minute ago, vdatanet said:

Did you try using default ports? 80 and 443

Using them where? In the browser they just redirect to 5000 and 5001.

[vdatanet 1617]

Just now, crusher11 said:

Using them where? In the browser they just redirect to 5000 and 5001.

Change Emby‘s public ports and forwading. Also disable upnp ports redirect in the router

[crusher11 1100]

7 minutes ago, vdatanet said:

Change Emby‘s public ports and forwading. Also disable upnp ports redirect in the router

What am I changing the forwarding to? Right now I have 80 to 80, 443 to 443, 7241 to 8096, and 4343 to 8920.

[vdatanet 1617]

11 minutes ago, crusher11 said:

What am I changing the forwarding to? Right now I have 80 to 80, 443 to 443, 7241 to 8096, and 4343 to 8920.

Set Emby's public ports to 80 and 443

Set router forwading 80 to 8096 and 443 to 8920

Did you disable Upnp port forwarding in the router to avoid DSM auto port mapping?

Edited July 11, 2021 by vdatanet

[vdatanet 1617]

Look at this:

[crusher11 1100]

11 minutes ago, vdatanet said:

Set Emby's public ports to 80 and 443

Set router forwading 80 to 8096 and 443 to 8920

Did you disable Upnp port forwarding in the router to avoid DSM auto port mapping?

Nothing changes except the port numbers. Success on the nonsecure port, failure on the secure port.

[vdatanet 1617]

Recap:

1. Disable UPnP auto port forwarding in the router
2. Set Emby's public ports to 80 and 443
3. Set router port forwarding  80 to 8096 and 443 to 8920

[crusher11 1100]

1 minute ago, vdatanet said:

Recap:

1. Disable UPnP auto port forwarding in the router
2. Set Emby's public ports to 80 and 443
3. Set router port forwarding  80 to 8096 and 443 to 8920

Yes, that's what I did.

Now I get success on domain:80 and failure to connect to domain:443, whereas previously I was getting success on domain:7241 and failure to connect on domain:4343.

Literally nothing has changed, we're just using different ports now.

[vdatanet 1617]

8 minutes ago, crusher11 said:

Yes, that's what I did.

Now I get success on domain:80 and failure to connect to domain:443, whereas previously I was getting success on domain:7241 and failure to connect on domain:4343.

Literally nothing has changed, we're just using different ports now.

and https://publicip. What happens?

[crusher11 1100]

Just now, vdatanet said:

and https://publicip. What happens?

The same as https://domain:443. "This site can't be reached. [IP] refused to connect. ERR_CONNECTION_REFUSED"