Recent Discussions
Anyone here know how to properly setup OVH's edge firewall
Unanswered
Polar bear posted this in #questions
215 messages
0 views
Polar bearOP
It is not intuitive at all, like i'm port forwarding as normal but it seems to block ports regardless when enabled?
Polar bearOP
its really weird
Like I'll add rules for port 80, 443 and 22 and then its not possible to access them
but when I remove them all I can only access 22 while 80 and 443 remains unreachable
for reference I'm using Pterodactyl panel on my VPS which should be port forwarded on both UFW and OVH
image.png
as shown here.
Polar bearOP
just genuinely no clue why it aint working cause everything is shown as working
Polish
Do you have the Edge Firewall enabled for the IP associated with your server?
If so, what do the rules associated with that edge firewall look like?
@Polar bear for reference I'm using Pterodactyl panel on my VPS which should be port forwarded on both UFW and OVH
Polish
Since you're using Pterodactyl, which uses Docker, it will attempt to manage it's own firewall rules directly with iptables, you shouldn't need to add them via ufw
What do your allocations in Pterodactyl look like?
show the edge firewall configuration
Polar bearOP
I'll post it after im in a lecture rn
Polar bearOP
finally not busy
@Darthmineboy show the edge firewall configuration
Polar bearOP
I disabled it and removed the rules but the rules were:
22, 2022, 443, 80, 8080 tcp set to mode authorize and and tcp status set to established
22, 2022, 443, 80, 8080 tcp set to mode authorize and and tcp status set to established
destination port*
@Polish What do your allocations in Pterodactyl look like?
Polar bearOP
idk how to check allocations within pterodactyl
ok tbh I don't have a lot of experience with docker and such
I did get ptero working once before by some miracle on an OCI server but oracle is now essentially impossible to get now which is why im renting an OVH server
Pteroq is running so the panel should be accessible though
Polar bearOP
ok figured out one of the issues, tcp status is set to established which only permits established connections and not new ones
Polar bearOP
but doesn't seem to be working stil
Polar bearOP
aight i think I figured it out, its a my end thing
@Polar bear @Darthmineboy here I recreated it
You need to add a rule to authorize tcp from/to any port with TCP status established and remove TCP status established from all existing rules
Polar bearOP
done that but still cant access the panel
Although im now getting a response when I ping the vps's tailscale IP
might have forgot to mention im doing panel access via tailscale
then you need to add tailscale to the edge firewall
Loading...
Loading...