192.168.x.x:1500

So I have a small local server running a website. It’s not public facing at all, has a static IP address on my WiFi LAN and can be accessed by any Linux machine. I can’t see it on any iPhone or Android device though

I’ve looked up tutorials on line, ensured my firewalls allow local sharing on the WiFi, double checked I can even ping the server successfully with nmap on Android

Any tips?

::edit:: typo in post, not when searching for IP on LAN

9 points

Are your phones on the same network? Same vlan? Firewall rules? VPN?

Does tcpdump on the server see the request?

permalink
report
reply
7 points
*

I get a lot of downvotes. I realize I say things that can be divisive. Why are people downvoting debugging steps? What’s divisive about that…

permalink
report
parent
reply
11 points

Don’t worry about downvotes.

permalink
report
parent
reply
4 points

I’m just trying to understand the rational. To me I downvote when the comment is against the community, or unproductive.

If I’m being a net negative I should know why! Usually I have a guess as to why, but when I don’t, I reach out so I can understand better. I do want lemmy to be a better place, so feedback is useful.

permalink
report
parent
reply
2 points

No tcpdump isn’t seeing the request… Thanks for the suggestion

permalink
report
parent
reply
3 points

Yeah, if phones go via WiFi and the computer is on a cable the IP ranges may differ and that would explain you can access only via one of the two.

permalink
report
parent
reply
1 point

Yeah everything (server, Linux clients, Android clients, other clients) is on the same WiFi network which is why this is extra frustrating since Linux just works like usual

permalink
report
parent
reply
1 point

might be your smartphone browser/system is using some kind of proxy. this could explain that you are able to ping, but the browser shows access denied. if no log entries are generated on the server when trying to access it via browser, it has to be something on client side or inbetween. on grapheneOS check: Settings - Network and Internet - Internet - Wifi-Settings - choose edit at top right - then advanced. If proxy is not set to none, change it and test again.

If this still doesn’t help, my last bet is some kind of duplicate IP

permalink
report
reply
1 point
*

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
HTTPS HTTP over SSL
IP Internet Protocol
SSL Secure Sockets Layer, for transparent encryption
VPN Virtual Private Network

5 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.

[Thread #928 for this sub, first seen 20th Aug 2024, 15:45] [FAQ] [Full list] [Contact] [Source code]

permalink
report
reply
3 points

Dunnon about iOS but some Android phones have a “network protection” config which uses a Google VPN, so it tends to block viewing the local network.

permalink
report
reply
1 point

Is there a setting for this? Yeah, I assume it’s some default setting I missed

(I’m seeing this issue on any Android distro, I’ve tried a few)

permalink
report
parent
reply
1 point

It’s listed as a privacy option on my pixel. It may be different for others but you could try searching the settings for “vpn” or “privacy.”

permalink
report
parent
reply
1 point

Hmm not seeing it on GrapheneOS

permalink
report
parent
reply
6 points

My guess is that you are making a typo. Like others have said 192.162.x.x is a public IP. You probably want something like 192.168.x.x which probably is more like 192.168.1.1/24 with the last 1 being its own number

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 3.5K

    Monthly active users

  • 3.4K

    Posts

  • 77K

    Comments