Web Page Access

[jltnol]

When the last update came in last February, I was having problems getting to the Indigo Web Pages, but needed up with an easy workaround. But with the latest update, I'm back to not being able to access my webpages.

When I use https://myreflector.indigodomo.net, I get to a log in page, sign in and then get the Indigo Touch for Web page.
If I add the ":8177" to the end, I get an "unable to connect" message. Port 8177 is open on my router and is forwarded to the IP address of my Indigo Server.

If I go to 192.168.6.102:8177 (which is the IP address of my sever, I'm asked to sign in, but still end up with the Indigo Touch for Web page.

If I go to my.ip.address:8177, I am asked to log in, but just get a "loading" page.
If I go to https://my.ip.address:8177, it hangs.
in both cases, this shows up in the log:
Web Server Warning access denied for request /v2/api/ws/log-feed from 20x.2x5.1x0.x1

It seems the only way I can get to an individual webpage is by going to the client and clicking on "Show In Browser" icon at the bottom, where this works:
http://127.0.0.1:8177/web/controlpage.h ... 1128697799

Other computers and browsers on my LAN behave the same way, except of course for the 127 method.

So just trying to figure out how to reach web pages with the newest version of the server, as none of my older methods are working....

[jay (support)]

Lots to unpack here.

When I use https://myreflector.indigodomo.net, I get to a log in page, sign in and then get the Indigo Touch for Web page.

Perfect, that's expected behavior.

If I add the ":8177" to the end, I get an "unable to connect" message. Port 8177 is open on my router and is forwarded to the IP address of my Indigo Server.

That is also expected behavior. The Indigo Web Server (IWS) runs on your server on port 8177. Our hosted reflector server creates an ssh tunnel to your IWS instance then forwards traffic from your reflector URL (on the default port for HTTPS) through the tunnel. So specifying 8177 on your reflector URL won't work.

If I go to 192.168.6.102:8177 (which is the IP address of my sever, I'm asked to sign in, but still end up with the Indigo Touch for Web page.

This is also expected behavior, because you are connecting on your local network directly to IWS (no reflector involved).

If I go to my.ip.address:8177, I am asked to log in, but just get a "loading" page.
If I go to https://my.ip.address:8177, it hangs.

I don't understand what my.ip.address is in your scenario, so you'll have to clarify. You just confirmed above that using the IP of the server works...

It seems the only way I can get to an individual webpage is by going to the client and clicking on "Show In Browser" icon at the bottom, where this works:
http://127.0.0.1:8177/web/controlpage.h ... 1128697799

You can use the same URL construction (with the correct hostname or IP) to get to that specific page. Use HTTPS if you are connecting with your reflector, or use HTTP when using the IP of your server and port 8177 on your local network.

Did I miss something?

[jltnol]

If I go to my.ip.address:8177, I am asked to log in, but just get a "loading" page.
If I go to https://my.ip.address:8177, it hangs.

The IP address in question is the IP address assigned by my service provider, or the domain name I have setup. Both the IP address or my domain name give the same results.

And while I can get to a specific webpage using this method:
http://mydomain.com:8177/web/controlpag ... =206316535,

I seem to recall reaching some kind of "landing page" if I entered just this:
http://mydomain.com:8177
where I could choose which page I wanted to see. With the above method, I'll have to create a bookmark for every page individually.... although I guess it might be possible to create my own landing page of some sort that would allow me to navigate to the page I wanted to see. This is different than in the past.

What am I missing....?

[DaveL17]

I'll just reiterate one point Jay is making here because it's key. When connecting to the Indigo reflector service, you MUST use `https` and when you're connecting locally (using the `localhost` or `127.0.0.1` loopback addresses or `192.168.x.x` ip, you MUST use `http`.

If you connect to the base address -- like `http://10.0.1.123:8176` or https://myreflector.indigodomo.net` -- you'll get the login for Indigo Touch Web. You can then click on the Pages tab to get a list of all your control pages. Clicking on one will spawn a new window with the control page displayed. As far as I know, the only way to open Indigo Touch Web directly to the Pages tab is to use the Web App functionality of Sonoma (which remembers the last visited tab). I don't know of a URL that takes you directly to the Pages tab in Indigo Touch Web.

If Jay says something that doesn't agree with the above, then Jay is right.

[jay (support)]

Ok, that's a different issue.

There currently isn't a way to load the Pages tab in ITW from a URL. We'll add that to the feature request list.

In the meantime, you can create a simple control page that just has links to the pages you want to show, then open that control page directly.

[jltnol]

Ok but.... please correct if I'm wrong.... was there ever some kind of "landing page"... like a list of indigo pages that would let you choose which webpage to visit?

[jay (support)]

The old web pages before we completely rewrote the web server were not an SPA (single page app), so each section had a unique URL. You could have gone directly to the URL for control pages to get directly to the list. It wouldn't have been the default page but you could have bookmarked it.

[DaveL17]

Okay, Jay and I did some digging and this will work with the current version of Indigo Touch Web (v2023.1.x):

Code: Select all

http://localhost:8176/index.html?tab=pages

Of course you'll need to refactor for your URL and port number as needed.

Current valid query args for "tab" are:

Code: Select all

http://localhost:8176/index.html?tab=devices
http://localhost:8176/index.html?tab=actions
http://localhost:8176/index.html?tab=variables
http://localhost:8176/index.html?tab=pages
http://localhost:8176/index.html?tab=logs

[jay (support)]

- this one is on me. I put the logic in there, but failed to get it documented (i.e. I didn't tell Dave)...

I had a vague recollection of doing it, but I'm old and it was 6+ months ago...

[jltnol]

I'm SURE I'm older, and no apology needed.

Glad to get this figured out..

THANKS

[jltnol]

So in retrospect, I think I'm the one that's confused. In the end, all this seems normal and right. I access Indigo web pages from the iOS app for the most part, and that still works exactly as I remember. Once I'm logged in thru the app, I can click on the Pages icon at the bottom, and there is my list of pages that I've been looking for. From there, I can tap on the page I want, and tapping on the upper left Control Pages icon brings me back to the page list. I'd say 95% of the time, I'm accessing pages from the iOS client.

I do occasionally look at pages from a web browser, and I think this is where things might be slightly different. Just as clicking on the Pages icon at the bottom of the Touch app you get a list of Indigo Pages, I vaguely seem to recall a similar list once I navigated to the web server from a browser. But not 100% sure about that.

Regardless, the device I use the MOST to access pages is my old iPad nailed to the wall by the back door, (and my phone) which runs the Touch app, so I can easily navigate to whatever page I'd like to see.