9

Hello,

when I wanted to call up a page with Orion that can only be accessed internally, I noticed that this page cannot be opened or that Orion then loads the whole time. However, when I try to access the page via Safari, it works. This happens with every page from the internal network. It looks like it doesn't really take over the DNS servers from the MAC network settings, is there a setting I missed or is this really a bug?

Orion Version 0.99.124.4.1-beta; MacOS-Ventura

  • Vlad replied to this.

    Danny_mtb Not sure what the bug as the post lacks steps to reproduce it. Can you be more specific?

      Hello Vlad ,

      I'm very sorry, we host some programs ourselves and to access them we just call the service's URL (via a domain name).
      Our internal DNS server then redirects to this internal ip and it can be called up in this way, but the service can also be accessed via the internet.

      The network automatically blocks requests coming from the same public IP as the router itself.
      When I try to go to this URL, Orion keeps loading and cannot open the page.
      I have the same problem with the other browsers, even if I don't use the standard DNS settings (i.e. directly from the network configuration) if I change them to 1.1.1.1, for example, the other browsers also load forever.
      This looks very much like a DNS configuration error to me. From what I've read, Orion also accesses the DNS settings of the connected network that are set directly by the network (like Safari), but it seems as if it doesn't take the correct DNS servers from the settings. Of course I can be wrong or it could be something else, but in Safari, Chrome, Firefox as well as other browsers do not have this problem if I keep the standard DNS settings.

      Even if I reinstall Orion or leave it in the default settings, the page loads forever until it breaks off at some point. Is it possible to see the used network settings directly somewhere in Orion?

      Thank you in advance for your answer, I hope I was able to describe it a bit better now.

      • Vlad replied to this.

        Danny_mtb You are however without being able to reproduce the problem we can't tell what is going on and whether a bug in Orion causes this.

          a year later

          Not sure if I have the same issue, but I can't access .local domains. When I type in http://qnap.local, I get the following error. It works in every other browser.

          Orion
          Version 0.99.129-beta (WebKit 619.1.11.111.2)
          Build date Oct 27 2024
          MacBook Pro (macOS Sequoia 15.1 build 24B83)

          • Vlad replied to this.

            chris027 How can we reproduce this problem? (doesnt work in other browser for me as well)

              Vlad

              I did additional testing and think it’s a routing issue that only seems to affect Orion for some reason.

              I can access 192.168.1.1 (my router) but I can’t access any other device by ip address or fqdn on this local network.

              All other browsers work perfectly.

              • Vlad replied to this.

                Perhaps I found one thing that's causing an issue. The machine on which this doesn't work has two network cards. One if on the 10.x.x.x network and the other 192.x.x.x network. Not sure why Orion has issues with this or if it's a red herring.

                  Vlad The only way I can think of reproducing this is to use a computer with two network interfaces that are on completely different network addressing schemes. I'm using 10.x.x.x and 192.x.x.x.

                  Perhaps this is such a niche issue that it isn't worth looking into though.

                    a month later

                    I don't know if I had exactly the same issue, but here is how I resolved it:
                    I hadn't been able to access .local domains or a local server via IP on macOS. Then it dawned on me that I might have clicked on "Don't allow" when a macOS popup asked 'Allow "Orion" to find devices on local networks?'. I checked the state of "Orion" in the local network section of "Privacy & Security" in System Settings. After giving permission to Orion my problem was solved.

                      a month later

                      Can I suggest that if you are accessing a local account on macOS it warns you of this. I have just spent a rather fruitless couple of days trying to connect to my synology. I am certain it used to have access, but at some point it reverted to not having access as above. I was just about to file the bug when I was led here.

                        a month later

                        Wow guys!

                        I can't reach my own router with your browser or any of my local servers! WTF!

                        • laiz replied to this.

                          chris027

                          It's NOT a niche issue!

                          AND you can't use the Bitwarden extension on local networks! Seriously!

                          Fix it!

                            iamliving
                            macOS settings -> Privacy & Security -> Local Network
                            Does Orion appear in that list and does it have the permission to find devices on your local network?

                              I'm running into the same issue. I cannot access any local resources (router, proxmox server, virtual servers, etc) through Orion on MacOS. Privacy&security ->Local Network is set correctly in MacOS settings.

                              I can however use these resources with safari. Is there a Setting in Orion that I overlooked?

                              /EDIT
                              Aha - fixed it by enabling compatiblity mode for specific websites.

                                When attempting to access my gateway's or PiHole's web interface via IP address, Orion prevents access, showing "You Are Not Connected to the Internet" (I am however connected to the Internet, as proved by submitting this bug). Switching to Safari I am able to access without issue.

                                Expected to be able to access the web interface.

                                0.99.131.0.1-beta

                                Sequoia (15)

                                  Merged 2 posts from Accessing IP address web interface results in "You Are Not Connected to the Internet".
                                    No one is typing