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

22 points

Are you sure you are typing the address in correctly on android/ios? 198.162.x.x isnt part of private IP space.

permalink
report
reply
17 points

Have you tried different browsers? You should also enter the full URL sometimes they’re a bit stupid nowadays. So http://192.168.x.x:1500/

Maybe the browsers bring their own VPN. Some process all traffic to make it more “mobile friendly”. Or they have some other kind of proxy.

permalink
report
reply
14 points

Also check to make sure the mobile browsers aren’t set to HTTPS only, or at least have an exception for that ip. I’ve seen that before several times.

permalink
report
reply
5 points

I’d curl from a machine on the same WiFi network as the phones just to confirm that HTTP is working. That way you’re not dependent on browsers that can be more finicky for debugging.

permalink
report
parent
reply
12 points

Some possibilities:

  1. WiFi has host isolation is enabled
  2. The network you’re connecting from is a guest wifi network
  3. You configured a firewall rule to isolate WiFi from LAN
  4. VLAN is enabled
permalink
report
reply
1 point

But if I can see the server on the same WiFi network from any Linux machine wouldn’t that ensure all those steps are OK?

permalink
report
parent
reply
1 point

I was assuming your server and Linux device were plugged in via Ethernet and your mobile devices were using WiFi. Now it sounds like your Linux system may be using the same access point.

It could be something as simple as your browser trying to send the address to a search engine instead of directly looking for the site.

When you’re trying to access it on mobile do you manually enter “http://” or “https://”? Those default to ports 80 and 443 respectively.

If you’re using nonstandard ports you may need something like “http://192.168.1.42:8080” to use http on port 8080 or any other nonstandard port.

Even if you are 100% sure your server is http or https try the other one to see if your error changes.

permalink
report
parent
reply
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
8 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
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
2 points

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

permalink
report
parent
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

  • 4K

    Monthly active users

  • 1.5K

    Posts

  • 13K

    Comments