View original (French)

Issue with opening ports 80 and 443 on Freebox Pop (full stack)

Solved
YoZ -  
 YoZ -

Hello,

I just acquired a Freebox Pop and I'm trying to configure access to my server.

I updated my OVH dynDNS directly from the Freebox => OK

(the ping of the URL correctly returns my IPv4)

I opened ports 80 and 443 in TCP / UDP as follows:

protocol: tcp

wan: 80

lan: 80

source ip: all

Destination: MyServer

The problem is that it does not work from the outside. However, on the LAN, when I try to access subdomain.mydomain.ovh it works well.

My server does indeed have a static lease configured.

What have I forgotten to do? It worked well with my Livebox.


5 réponses

Réponse 1 / 5
brupala Posted messages 111947 Registration date   Status Membre Last intervention   14 422
 

Hello

I just got a Freebox Pop,

No, the Freebox doesn't belong to you; it belongs to Free and is part of their network.

As for the rest, it's more complicated if you're really full stack, especially since it looks like you've done everything correctly.

Especially since, in principle, it works from the outside but not from the inside, but with the Freebox, I have doubts because I tested it myself; in fact, we need a slightly different redirection than usual that allows the external address to be redirected internally.

What is the returned error?

Otherwise, in IPv6?

And there you go...

But damn, what a pain those line breaks are!
1
Réponse 2 / 5
bazfile Posted messages 58430 Registration date   Status Modérateur Last intervention   20 245
 

Hello.

Did you request a full stack IP address through your Freebox subscriber space? If so, did you restart your Freebox?

bazfile
Moderator/Security Contributor.
A hello, a response, a thank you are always appreciated.
1
brupala Posted messages 111947 Registration date   Status Membre Last intervention   14 422
 

Hello,

uh, it's in the title apparently?

0
bazfile Posted messages 58430 Registration date   Status Modérateur Last intervention   20 245 > brupala Posted messages 111947 Registration date   Status Membre Last intervention  
 

There has already been a similar case; it was someone who switched from Orange to Free and who had not activated this option, that’s why I sent this message.

0
Réponse 3 / 5
YoZ
 

Well, problem solved. The issue was indeed with my Reverse Proxy that did not handle IPv6.

I took the opportunity to switch to NPM (Nginx Proxy Manager) and everything is working perfectly now.

So the problem was indeed not with the FBX.

Thanks to everyone who offered their help!
1
Réponse 4 / 5
YoZ
 

Yes, I confirm, V4 Full Stack requested in the customer area, Box restarted (multiple times lol).

I forgot to mention some other details:

  • Truenas Core server
  • NGinx Reverse proxy jail on which I disabled IP V6 after which I was able to access my subdomains on LAN.

What surprises me is that in the Freebox, if I look at the Connectivity tab of my Nginx VM, I can see my configured V4 IP in the port forwarding but also 2 V6 IP addresses! Yet, I clearly disabled it on this VM :/

I called Free's hotline but the guy didn’t understand that opening a port allows access to my server from the internet xD
0
brupala Posted messages 111947 Registration date   Status Membre Last intervention   14 422
 

Does the dyndns ovh work well?

Do you have a domain with ovh to point to it?

You are talking about a vm, does the vm have an address in the fbx network or do you redirect to the physical address of the nas, do they each have their own address?

1
YoZ > brupala Posted messages 111947 Registration date   Status Membre Last intervention  
 

Yes, the dyndns ovh works well. I see the last update date a few minutes ago, at ovh, I can see the box's IPv4 and the ping of the ovh url correctly returns the box's IP.

The VM has its own IPv4 (I need to check if the IPv6 visible in the FBX is that of the NAS or if it has nothing to do with it!)

0
brupala Posted messages 111947 Registration date   Status Membre Last intervention   14 422 > YoZ
 

Let's forget about ipv6 for now, it's not your topic at the moment, although it would be a good idea to use it.

So if you ping the ovh dyn dns, it responds, is it a domain of yours?

After that, I think we'll need details on everyone's private addresses to move forward with a diagnosis, it's still vague at this point.

1
Réponse 5 / 5
yg_be Posted messages 23437 Registration date   Status Contributeur Last intervention   Ambassadeur 1 587
 

Hello,

I would try 8080 on WAN and 80 on LAN, and of course, add ":8080" to the link.
0
brupala Posted messages 111947 Registration date   Status Membre Last intervention   14 422
 

Hello,

I don't think the fbx listens on 80 on the wan...

By default, remote administration is done on 337 (http) and 360 (https)

0