Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Can't Connect via LAN

    Emby
    2
    6
    58
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      Ropyro last edited by

      Howdy --

      I've set up Emby and everything is working fine except that while I can access the server from an external IP, I can't connect to it within the LAN. I've tried connecting to the server's IP/port number through a browser and through the FireTV app. The FireTV app isn't finding the server automatically and it doesn't like the IP/port numbers I'm giving it manually. Same is true via browser, however the browser works when using the domain name because I modified the hosts file to make that work.

      Any idea what I'm missing?

      Thanks, in advance.

      R girish 2 Replies Last reply Reply Quote 0
      • R
        Ropyro @Ropyro last edited by

        @Ropyro Was able to get it working by setting up Emby Connect. Feeling a bit like that's a workaround and not a real solution, but I'll take it.

        1 Reply Last reply Reply Quote 0
        • girish
          girish Staff @Ropyro last edited by

          @Ropyro Does your router support hairpin nat ? See https://docs.cloudron.io/troubleshooting/#hairpin-nat

          R 1 Reply Last reply Reply Quote 0
          • R
            Ropyro @girish last edited by

            @girish Sorry for the delay. It doesn't, unfortunately.

            girish 1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @Ropyro last edited by

              @Ropyro Ah ok, that's the root of the issue. I too had a situation in the past where my router didn't support hairpin nat. The issue roughly is that the domain name (emby.myserver.com) points to an external IP. What you have to do is to somehow make a setup where it points to your internal IP when DNS requests are made in your internal network.

              In my case, my router was also my DNS server. I could simply add an entry emby.myserver.com there and point it to my internal server IP and that was it.

              R 1 Reply Last reply Reply Quote 1
              • R
                Ropyro @girish last edited by

                @girish OK, thanks. I'll look at that. My is absolute garbage in that I'm almost completely locked out of customizing anything with it. My ISP clearly wants full control. I appreciate your responsiveness!

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Powered by NodeBB