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

  • Björn Tantau@swg-empire.deEnglish
    2·
    3 months ago

    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.

  • Shimitar@feddit.itEnglish
    1·
    3 months ago

    I have a very similar issue. Seems like Android will bypass your DNS resolver and thus cannot resolve your local names.

    I have my home services on “home.my domain.com” accessible from outside and re-mapped to “192.168.0.1” (my internal server IP) at home, and all PCs can access it while all android phones can only resolve to the public IP.

    I feel it’s something related to DoT or similar but haven’t yet dig in that.

  • Possibly linux@lemmy.zipEnglish
    1·
    3 months ago

    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

  • Finadil@lemmy.worldEnglish
    1·
    3 months ago

    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.

    • Prison Mike@links.hackliberty.orgEnglish
      2·
      3 months ago

      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.

  • hungover_pilot@lemmy.worldEnglish
    1·
    3 months ago

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

  • shrugs@lemmy.worldEnglish
    11·
    3 months ago

    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

  • zelifcam@lemmy.worldEnglish
    0·
    3 months ago

    Your network is probably configured with inconsistent subnets / netmasks. iOS / Android are on WiFi and getting a different subnet/netmask than your severs.

    Edit: What does pinging the server with nmap mean? Are you checking open ports or pinging the server? That doesn’t make sense or at least leaves us with more questions with the way you worded that. Although the nmap utility can provide both of those answers, I’m not sure that’s what you meant. Technically nmap and ping are two different tools.

      • zelifcam@lemmy.worldEnglish
        0·
        3 months ago

        Same netmask?

        When asking for network troubleshooting assistance, super useful to provide ANY kind of network info. So far we have WiFi and same subnet. Yet absolutely no details which are necessary to help form questions or provide answer.

        Can you post the IP Netmask and Gateway of your Linux server and one of your mobile devices that can’t view the server?

        Can you ssh into the Linux server from your mobile device?

          • zelifcam@lemmy.worldEnglish
            0·
            3 months ago

            Then there has to be a firewall, web server whitelist or some kind of configuration issue with the service being hosted. Because according to all your responses they are on the same WiFi with the same subnet/gateway/netmask.