I do Have a Raspberry PI 3B with Domoticz V4.10717 on it
It worked fine on my KPN Experiabox V10, internaly and externaly with port 8080.
This week I changed from KPN to Solcon and now I have a FRITZ!Box 7530.
Internaly Domoticz works.
Externaly it doesn't work.
In the FRITZ!Box I have tried port forwarding TCP, UDP, HTTP, HTTPS, all kind of situations. Nothing works.
I have called the technical support of Solcon.
They see that my port is open. But, they also can't reach my Raspberry PI.
What must I do to let it work externaly?
Thanks in advance,
Rob
FRITZ!Box 7530 Port Forwarding doesn't work wit PI
Moderator: leecollings
-
- Posts: 80
- Joined: Sunday 29 November 2015 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V4.9700
- Location: Halle, the Netherlands
- Contact:
- erem
- Posts: 230
- Joined: Tuesday 27 March 2018 12:11
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Amsterdam/netherlands
- Contact:
Re: FRITZ!Box 7530 Port Forwarding doesn't work wit PI
Can you post the Fritz.os version, and the forwarding rule(s) you defined?
This is definitely a router issue, not a Domoticz issue.
This is definitely a router issue, not a Domoticz issue.
Regards,
Rob
Rob
-
- Posts: 80
- Joined: Sunday 29 November 2015 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V4.9700
- Location: Halle, the Netherlands
- Contact:
Re: FRITZ!Box 7530 Port Forwarding doesn't work wit PI
Het betreft versie FRITZ!OS: 07.12
-
- Posts: 80
- Joined: Sunday 29 November 2015 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V4.9700
- Location: Halle, the Netherlands
- Contact:
Re: FRITZ!Box 7530 Port Forwarding doesn't work wit PI
If I check my external port with a Port Forward Tester like:
(https://portchecker.co/check)
(https://www.portcheckers.com/)
(https://www.yougetsignal.com/tools/open-ports/)
then I only can open with:
port number 80.
For example, if I configure my FRITZ!Box for an ESP8266 sensor module as:
Port ESP8266 (intern): 80 - 80
Port extern: 80
The port tester says that the port is open.
================================================
If I configure my FRITZ!Box as:
Port PI (Domoticz) (intern): 8080 - 8080
Port extern: 80
The port tester says that the port is closed.
(https://portchecker.co/check)
(https://www.portcheckers.com/)
(https://www.yougetsignal.com/tools/open-ports/)
then I only can open with:
port number 80.
For example, if I configure my FRITZ!Box for an ESP8266 sensor module as:
Port ESP8266 (intern): 80 - 80
Port extern: 80
The port tester says that the port is open.
================================================
If I configure my FRITZ!Box as:
Port PI (Domoticz) (intern): 8080 - 8080
Port extern: 80
The port tester says that the port is closed.
- andreo
- Posts: 45
- Joined: Friday 07 August 2015 21:00
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.3
- Location: Anna Paulowna, Netherlands
- Contact:
Re: FRITZ!Box 7530 Port Forwarding doesn't work wit PI
These are my setting on a Fritzbox 7490
Latest version of Domoticz and more running on Docker|Raspberry Pi 4-B 8GB Bookworm|RF-Link|Klik Aan Klik Uit|Nefit easy|ESPeasy|P1 power meter|S0PCM-5 through Ser2Net|Alecto WS5500|FrtizBox|Satel Integra|Solis
Greetz Andre.
Greetz Andre.
-
- Posts: 80
- Joined: Sunday 29 November 2015 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V4.9700
- Location: Halle, the Netherlands
- Contact:
Re: FRITZ!Box 7530 Port Forwarding doesn't work wit PI
I made a simple webserver on an ESP8266, two leds, two buttons in the webinterface.
I can give this ESP almost any internal port number in the sketch as well as almost any external port number in the FRITZ!Box, and it works.
But my PI is not reachable from outside.
I notice that the FRITZ!Box gives the PI also a so called IPv6-interface-ID.
Can that be the problem?
It drives me nuts!
I can give this ESP almost any internal port number in the sketch as well as almost any external port number in the FRITZ!Box, and it works.
But my PI is not reachable from outside.
I notice that the FRITZ!Box gives the PI also a so called IPv6-interface-ID.
Can that be the problem?
It drives me nuts!
Who is online
Users browsing this forum: No registered users and 1 guest