Need help with OPNsense and Unraid connectivity

mushtafa

mushtafa

mushtafa

Soldato
Joined
17 May 2013
Posts
2,976
Location
West Sussex, UK
Any networking gurus here?

Came back from holiday to find my network had partially gone down.
I believe the fault to be my port forwarding not working. I'm now on a fresh install of OPNsense, and it's still not working. (I'm now wondering if it's a networking fault with Unraid?

I'm about 20 hours in to troubleshooting, and still non the wiser.

Can anyone assist?

EDIT:
I lost outside connectivity via my own URLs via Xginx Proxy Manager, and Plex remote access.
I concentrated on the Plex fault - considering that should be the easier fault to fix. I restarted the docker service, force updated the docker containers, updated unraid, even reinstalled the container.
Still no luck.
Looking at OPNsense being the fault now, I found lots of IO failure messages. Suspecting a bad HDD or cable/connection, I threw a replacement SSD in the system. IO errors have now gone.
Using my config file, I was still unable to get Plex remote access working.
I did a fresh install of OPNsense, and still no good. I've followed numerous guides online, without success.
The remote access now shows it's OK for 10-15 seconds before failing and going red again.

I'm not sure where to go now, or what to blame for the issue. Unraid/docker connectivity issue, or OPNsense rules/NAT issue?
 
Last edited:
I'm more looking for someone who's willing to help who I can message with details and potentially even remote into my system to assist.

Not sure how a VPN will assist with Plex remote access and Nginx Proxy Manager....
 
Yeah, that would be ideal. The issue might be found within a few minutes.
I will edit my original post though with all the info
 
Yes, Plex is working internally.
yes, 32400 set.
OPNsense is installed on it's own appliance.

Using port checking websites shows the port closed
 
Been doing more reading... Would this suggest I'm behind CGNAT? Seems like a lot of hops. And the 172. IP range are private aren't they?

Code: 
 traceroute to www.google.com (142.250.187.228), 64 hops max, 40 byte packets
TTL    AS#    Host    Address    Probes
1    AS0    172.16.32.126    172.16.32.126    6.646 ms
3    AS0    172.16.32.178    172.16.32.178    6.968 ms
4    AS16353    217.146.102.180    217.146.102.180    10.505 ms
6    AS16353    v948.lon1-gw1.merula.net    217.146.96.1    6.997 ms
7    AS0    195.66.236.125    195.66.236.125    7.426 ms
8    AS15169    192.178.97.187    192.178.97.187    6.924 ms
9    AS15169    142.251.54.49    142.251.54.49    7.067 ms
10    AS15169    lhr25s34-in-f4.1e100.net    142.250.187.228    7.195 ms
 
Can't believe I've been fighting this for hours and days and it was the ISPs fault!

They must have changed something their end recently, has been fine for the 11 month previously. (And I pay extra for a static IP address :rolleyes:)
 
A reboot gave me a different IP, but not what has been allocated to me. I'll have to speak with Merula support once they're open again
 
Amazingly I managed to speak to someone last night, but he said it was too technical for him and someone would be in touch on Monday.
Seems like good customer service, so hopefully will be up and running again very soon.
 
I received an email yesterday evening saying they had made background changes. They've told me I now need to pay extra for a static IP. (I already do - that's another argument).

My question; if they assign me another static IP, could I still be behind CGNAT and have issues or does the static bypass the CGNAT stuff?
 
They told me they made some changes behind the scenes and 'accidently' changed mine too. They did fix the issue pretty quick once I contacted them.
 
You must log in or register to reply here.
Back
Top Bottom