Switch and reverse proxy issue

chili

chili

chili

Associate
Joined
19 Mar 2011
Posts
822
I am very new to tinkering shall we say and i have an issue that i just cannot for the love of god figure out, my items listed below

Router is tp-link ac1200
synology nas
raspberry pi 3b
desktop pc
switch tp-link tl-sg105s

so because of where my things are situated indoors i bought an unmanaged switch to act as an extension. my simple project was to self host vaultwarden, i tried to do this on my nas but failed miserably
and in my frustration just put it down to age 63 and lack of knowledge. unbeknown to me at the time it was the switch causing the issue, and still is.
i bought the Pi 2nd hand to fiddle with and also to try and self host vaultwarden on it, bingo it worked (the Pi was wired direct into the back of the router while i set this all up via ssh) it was not until i i attached the Pi to the switch in a more
convenient position that it then failed to connect to my self hosted container, thinking i had done something wrong i spent the last 3 days trying to figure out my mistakes.
My mistake was simple i attached it to the switch.

So what i have discovered is this if i have my pc and the Pi and the nas all wired into the switch all 3 devices will work however what does not work is any of theses devices connecting via https reverse proxy to the docker/portainer container?

if i plug the pc into the router direct and the pi into the switch the reverse proxy works and i connect via https to my container same applies to the nas.
when all 3 are connected to the switch i can connect to the http web gui's of the apps used ie docker/portainer/nginx/nas but not the https
the pc Pi and nas all have their own ip's router and open ports are all working as should.

Ideally i would like to have the pc and the pi on the switch and work happily along side each other.

anyone any idea's of a solution?

many thanks in advance
 
chili said:
I am very new to tinkering shall we say and i have an issue that i just cannot for the love of god figure out, my items listed below

Router is tp-link ac1200
synology nas
raspberry pi 3b
desktop pc
switch tp-link tl-sg105s

so because of where my things are situated indoors i bought an unmanaged switch to act as an extension. my simple project was to self host vaultwarden, i tried to do this on my nas but failed miserably
and in my frustration just put it down to age 63 and lack of knowledge. unbeknown to me at the time it was the switch causing the issue, and still is.
i bought the Pi 2nd hand to fiddle with and also to try and self host vaultwarden on it, bingo it worked (the Pi was wired direct into the back of the router while i set this all up via ssh) it was not until i i attached the Pi to the switch in a more
convenient position that it then failed to connect to my self hosted container, thinking i had done something wrong i spent the last 3 days trying to figure out my mistakes.
My mistake was simple i attached it to the switch.

So what i have discovered is this if i have my pc and the Pi and the nas all wired into the switch all 3 devices will work however what does not work is any of theses devices connecting via https reverse proxy to the docker/portainer container?

if i plug the pc into the router direct and the pi into the switch the reverse proxy works and i connect via https to my container same applies to the nas.
when all 3 are connected to the switch i can connect to the http web gui's of the apps used ie docker/portainer/nginx/nas but not the https
the pc Pi and nas all have their own ip's router and open ports are all working as should.

Ideally i would like to have the pc and the pi on the switch and work happily along side each other.

anyone any idea's of a solution?

many thanks in advance
Click to expand...
I'll be honest, if its an umanaged switch and their are no fancy DMZ bits setup on the router it shouldn't make a difference to be since they should all be on the same subnet so it doesn't/shouldn't matter what port they are connected to or if the switch is in the way.

Just checking, there is no DMZ on the router (Port with a different network/set of rules) which you could potentially be connected your Pi to and switch?

Alternatively, the switch could potentially have some weird issue with traffic that just happens to appear in your setup, it wouldn't be the first time I've heard of something like this happening but it would be very strange.
 
TechMinerUK said:
I'll be honest, if its an umanaged switch and their are no fancy DMZ bits setup on the router it shouldn't make a difference to be since they should all be on the same subnet so it doesn't/shouldn't matter what port they are connected to or if the switch is in the way.

Just checking, there is no DMZ on the router (Port with a different network/set of rules) which you could potentially be connected your Pi to and switch?

Alternatively, the switch could potentially have some weird issue with traffic that just happens to appear in your setup, it wouldn't be the first time I've heard of something like this happening but it would be very strange.
Click to expand...
Router is pretty much stock settings, everything is on my home network, only 1 network
like i say if i seperate everything it works, like now for example my nas is plugged direct into the back of the router, the switch is connected to a 5mt cable that is plugged into the router, my Pc is plugged into the switch the reverse proxy settings are working just fine, as soon as they are all in the switch it breaks :(
i have 1 dmz setting in my router under nat forwarding thats just called dmz and its disabled with a dmz host ip address of 0.0.0.0
 
chili said:
Router is pretty much stock settings, everything is on my home network, only 1 network
like i say if i seperate everything it works, like now for example my nas is plugged direct into the back of the router, the switch is connected to a 5mt cable that is plugged into the router, my Pc is plugged into the switch the reverse proxy settings are working just fine, as soon as they are all in the switch it breaks :(
i have 1 dmz setting in my router under nat forwarding thats just called dmz and its disabled with a dmz host ip address of 0.0.0.0
Click to expand...
That is really quite bizarre, if you have a different switch spare somewhere I would try that and see if the issue persists as since it's unmanaged it shouldn't make a bit of difference to the setup since it is just allowing more devices to connect on the same network.
 
so i found someone else with the same issue as myself below is their initial post and the issue

I can't port forward (NAT) on my router to a device behind my TL-SG1008P.
It works fine when I connect the device instead (in front) of the switch but not after the switch.
When using the switch I can access the ports from other devices in my LAN but not from outside, outside I can only access devices that are not behind the switch.
The IP and MAC of the device doesn't change depending on if its behind the switch or not.

and their conclusion

I found the issue: I can only connect to my own public IP through connections not coming from my LAN, only other LANs

so is their away to get round this
 
You must log in or register to reply here.
Back
Top Bottom