-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access hosted filebrowser on external devices within a LAN #3234
Comments
Try disabling "AP Isolation" (also known as "Client Isolation" or "Guest Mode") in your router settings |
I am not sure if that would be the appropriate setting, as the only port that is unavailable on other devices within my network is whatever port is being utilized for |
I have successfully figured out that I must listen to IP address |
The application simply defaults to the “loopback” IP address at |
Description
I am trying to utilize my
wlp2s0
IP address to access thefilebrowser
application and the only device that I can access the application from in my Local Area Network (no port forwarding by the way, so only on my LAN) is the actual localhost computer.Expected behaviour
I expected to be able to launch the
filebrowser
application by navigating to the appropriate website and port on my other devices, but that had continuously failed. I had attempted to change the IP address to listen on to mywlp2s0
address and not to the default loopback address which is always127.0.0.1
.What is happening instead?
Sorry, but I have not attempted to use verbose mode with this application.
Additional context
On my other devices on my Local Area Network (LAN), each external system claims that the "server cannot be found" or an identical issue.
How to reproduce?
Visit
http://<address>:<port>
on a device that shares the network or includes access to the IP address within the network (WAN with port forwarding, otherwise LAN).Files
There is no specific file to be pinpointed in this issue. I am not sure if this is a problem with the Go code, and even then, I do not have significant Go language experience and would be unsure which Go file to blame.
The text was updated successfully, but these errors were encountered: