this post was submitted on 20 Aug 2024
45 points (94.1% liked)

Selfhosted

40329 readers
419 users here now

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!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
45
Local server can't be seen on Android or iOS, but can on any Linux device (reddthat.com)
submitted 3 months ago* (last edited 3 months ago) by shamrockpreacher5@reddthat.com to c/selfhosted@lemmy.world
31 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] Agility0971@lemmy.world 5 points 3 months ago* (last edited 3 months ago) (1 children)
  1. network interface - check
  2. dns - not applicable
  3. firewall - check
  4. ping - check
  5. navigating to the web site - fail

There are two causes here. Either server fucks it self over or the client fucks itself over. For server check logs, for client: check spelling, specify full protocol and try different browser to pinpoint the problem. It would be great to see the full ip address output from 'ip -c a' on both client and server.