Thank you Mohammed, I hope I just open the port 80 for http and 443 for the https. I don`t want you to have unnecessary ports open. 😊 I hope to make sense the joke.
thanks for this vid, but I'm getting this when I'm trying to create SSL cert using a duck dns subdomain --> There is a server found at this domain but it does not seem to be Nginx Proxy Manager. Please make sure your domain points to the IP where your NPM instance is running.. Any thoughts? ta
This error message suggests that the domain you are trying to create an SSL certificate for is not correctly pointing to your Nginx Proxy Manager instance. Here are some steps you can take to troubleshoot the issue: Make sure your DuckDNS subdomain is correctly configured to point to your public IP address. You can check this by entering your subdomain in a web browser and verifying that it connects to your TrueNAS system. Check that your Nginx Proxy Manager Docker container is running and accessible. You can do this by accessing the container's web interface by navigating to the IP address and port of the container (usually [container IP]:81/). Verify that your Nginx Proxy Manager settings are correct, including the domain name and port numbers you are using. Double-check that your firewall is properly configured to allow traffic through to your Nginx Proxy Manager container. If you have checked all of these steps and are still experiencing issues, you may need to further troubleshoot your networking and DNS settings.
Check if all required port for this application is open at your router, if not, this will not work well. After you set up the port forwarding, try to see if the port is really open.
The first time that you try to access show NGINX 502 Bad Gateway. In my mind came few possibilities, normally is the connection between the PHP and the FPM. You can try to install “sudo apt install php-fpm“ Also try to update de system “sudo apt update & upgrade”. And re-instal the NGINX. If this do not fix the issue. Could you please send a copy of the log? This can be found in the container Log. In this way we can see what is not working in the way that should be.
Wojciech, I look this error on the internet, the only thing that I could find is related to the Cloudflare, If this is the case, you should change the policy for Full SSL encryption. If you are using the DuckDNS, send the container Log, so I can see the issue.
Can u expand on adding cerificate please. I am addimg one successfully but still getting bad certificate when navigating to it
Can't thank you enough to open the door to the world for me!!!
Thank you Mohammed, I hope I just open the port 80 for http and 443 for the https. I don`t want you to have unnecessary ports open. 😊
I hope to make sense the joke.
thanks for this vid, but I'm getting this when I'm trying to create SSL cert using a duck dns subdomain --> There is a server found at this domain but it does not seem to be Nginx Proxy Manager. Please make sure your domain points to the IP where your NPM instance is running.. Any thoughts? ta
This error message suggests that the domain you are trying to create an SSL certificate for is not correctly pointing to your Nginx Proxy Manager instance. Here are some steps you can take to troubleshoot the issue:
Make sure your DuckDNS subdomain is correctly configured to point to your public IP address. You can check this by entering your subdomain in a web browser and verifying that it connects to your TrueNAS system.
Check that your Nginx Proxy Manager Docker container is running and accessible. You can do this by accessing the container's web interface by navigating to the IP address and port of the container (usually [container IP]:81/).
Verify that your Nginx Proxy Manager settings are correct, including the domain name and port numbers you are using.
Double-check that your firewall is properly configured to allow traffic through to your Nginx Proxy Manager container.
If you have checked all of these steps and are still experiencing issues, you may need to further troubleshoot your networking and DNS settings.
I tried to install php-fpm, but I'm still getting a bad gateway. Any idea on what I could do?
Check if all required port for this application is open at your router, if not, this will not work well.
After you set up the port forwarding, try to see if the port is really open.
When i try to sighn in for first time with nginx says bad gateway.how do i fix
The first time that you try to access show NGINX 502 Bad Gateway. In my mind came few possibilities, normally is the connection between the PHP and the FPM.
You can try to install “sudo apt install php-fpm“
Also try to update de system “sudo apt update & upgrade”. And re-instal the NGINX.
If this do not fix the issue. Could you please send a copy of the log? This can be found in the container Log. In this way we can see what is not working in the way that should be.
This is great video
Thank you T B. :)
Struggling to figure out the port forwarding >.>
Whatever I do I get error. "err_too_many_redirects" How will I fix it?
Wojciech, I look this error on the internet, the only thing that I could find is related to the Cloudflare, If this is the case, you should change the policy for Full SSL encryption.
If you are using the DuckDNS, send the container Log, so I can see the issue.
why the french accent?
its portuguese
@@lussor1 ewww
Yeah more Portuguese accent. :)