Welcome! Log In Create A New Profile

Advanced

Problems with nginx + router(Fritzbox) portforwarding

Posted by Nachtschatten 
Problems with nginx + router(Fritzbox) portforwarding
May 07, 2017 08:26AM
(Sorry for bad English, I'm German)
Hello,
I'm not sure if this forum is the right one to ask, but I struggle to setup a webserver with nginx:
I installed nginx (and a few other programs) on my raspberry pi and configured a portforwarding on my router (Fritzbox) (portForwarding.png). After that I used ddnss.de (a dynDNS service) to bind my IP 78.**.**.** to ****.ddnss.de.
If I type http://192.168.178.66 (local ip of the raspberry pi) into the webbrowser I see the "Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required." page - everything works. But if I type http://78.**.**.** into the webbrowser or ****.ddnss.de the browser tells me that it can't reach the site.

Does anyone know how to fix this problem /has some links for explanation?

System Information:

PC used for nginx webserver: Raspberry Pi 3
Operating System: Linux (Ubuntu)
http://myip.is -> 78.**.**.**
ifconfig on the raspberry pi -> 192.168.178.66
Intention: Setting up nextcloud and nginx on the Raspberry Pi 3

$ host -t A ****.ddnss.de
****.ddnss.de has address 78.**.**.**

$ host -t AAAA ****.ddnss.de
****.ddnss.de has no AAAA record

$ ping ****.ddnss.de
PING ****.ddnss.de (78.**.**.**) 56(84) bytes of data.
-> no respnse

$ ping 78.**.**.**
PING 78.**.**.** (78.**.**.**) 56(84) bytes of data.
-> no response
Attachments:
open | download - portForwarding.png (5.1 KB)
Re: Problems with nginx + router(Fritzbox) portforwarding
May 15, 2017 06:45PM
i cannot explain why the routing does not working but you can work in your local network with your server do omething like this:

Don´t work with the external IP adress, rather work with domain names.
You have checked the dns and working fine (external) check it with anoter internet connection (like smartphone)
If DNS in the internet work fine, so your server is working in the i-net.

So you can use an internal DNS and bind your domain to your loacal ip adress 192.x.x.x

or

make an host entry

192.x.x.x. yourdomain.de

in

windows: C:\Windows\System32\drivers\etc\hosts (run editor as administrator/als Administrator ausführen and load the host file)
linux /etc/hosts

on all your local net clients.

This are the steps i am working since 2002 and serving services at DSL Deutsche Telekom.
Today iam working with static ip.
If you want a serious service take a business product 20€ higher and static ip. Further you can work with an accepted smtp relay.
You can setup a lots of domains like registering and delegating to your static ip.
and... don´t work unencrypted - use SSL to prevent other errors.

Best regards from Solingen, Germany
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 125
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready