# ASL Web UI - not loading

**URL:** <https://community.allstarlink.org/t/asl-web-ui-not-loading/25190>\
**Category:** AllStarLink\
**Created:** [November 14, 2026, 6:47am UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190 "2026-11-14T06:47:32Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\
**Post date:** [November 14, 2026, 6:47am UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/1 "2026-11-14T06:47:32Z")

</div>

I'm running a pi4 w ASL3 and latest updates. The cockpit does not say what version of Linux is running but instructions says existing appliance users only need be updated. The instruction for address is confusing- the examples don't match up: " ...open **`https://<your-node>/`** - for example `https://node63001.local/`"

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 3:48pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/2 "2026-11-14T15:48:33Z")

</div>

I'm not sure which part you're confused about. If you named your system "node63001" when you imaged it, then it should be on your network as `https://node63001.local/`. When you browse to it, you should get the appliance landing page.

---

<div class="post-metadata">

**Author:** ![N5NZZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5nzz/32/5209_2.png) [@N5NZZ](https://community.allstarlink.org/u/N5NZZ)\
**Post date:** [November 14, 2026, 8:59pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/3 "2026-11-14T20:59:44Z")

</div>

I just got the email link a few days ago .. I must say, initial installation instructions are quite incomplete .. the nginx settings are ambiguous at best .. and accessing the web UI will not show up as https as it says it would …

---

<div class="post-metadata">

**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\
**Post date:** [November 14, 2026, 9:03pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/4 "2026-11-14T21:03:59Z")

</div>

Hi- The first example suggests " **`https://<your-node>`**" instead of " **`https://<your-node>.local/`** It does not matter- I get it based on the 2nd example- just threw me bc they don't match.

My node hostname from cockpit is ASL48654 and when entered does not load a web page  
[https://ASL48654.local/](https://ASL48654.local/)

I can get to the cockpit using the ip and port 9090. Not sure what the issue is. I turned off my VPN just to test and then [https://ASL48654.local/](https://ASL48654.local/) just loads the cockpit page. Odd bc I use cockpit, Allscan, Herald via ip with VPN on. I guess it interferes w hostname addresses for some reason and not ip based addresses. The Pi and PC are on the same LAN, nothing unique there.  
Thx

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 9:35pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/5 "2026-11-14T21:35:48Z")

</div>

> [@N5NZZ](#):
>
> I just got the email link a few days ago .. I must say, initial installation instructions are quite incomplete .. the nginx settings are ambiguous at best .. and accessing the web UI will not show up as https as it says it would

You should be able to simply `include /etc/asl-web-ui/nginx.conf;` in the relevant `server { }` blocks and it "just works". At least that's been my testing experience. I'd like to know what didn't work.

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 9:37pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/6 "2026-11-14T21:37:27Z")

</div>

> [@KK6QMS](#):
>
> I can get to the cockpit using the ip and port 9090. Not sure what the issue is. I turned off my VPN just to test and then [https://ASL48654.local/](https://ASL48654.local/) just loads the cockpit page. Odd bc I use cockpit, Allscan, Herald via ip with VPN on. I guess it interferes w hostname addresses for some reason and not ip based addresses. The Pi and PC are on the same LAN, nothing unique there.

That's a little confusing but only because everyone's network will behave differently. The `.local` assumes you're running the appliance which means the mDNS is sending the name out on your LAN every so often. Your system has to notice it and start using it. Also, using any sort of VPN will break mDNS. The alternative is to go to a known hostname and/or IP address as documented.

---

<div class="post-metadata">

**Author:** ![KK6QMS](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6qms/32/1356_2.png) [@KK6QMS](https://community.allstarlink.org/u/KK6QMS)\
**Post date:** [November 14, 2026, 10:46pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/7 "2026-11-14T22:46:52Z")

</div>

Looked at github page then the manual- the address is listed as "https:///asl-web-ui/" at [Installing and Logging In - AllStarLink Manual](https://allstarlink.github.io/web-ui/install/)

The orig post here left out the /asl-web-ui/ portion of the address.

When I use that address via ip I get an Apache message saying:

"Not Found  
The requested URL was not found on this server.

Apache/2.4.71 (Debian) Server at 192.168.1.188 Port 443"

Is there a way to locate and verify the web ui is installed properly? I looked in var/www but nothing there and I have no idea where else to look. Thx.

---

<div class="post-metadata">

**Author:** ![N5NZZ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5nzz/32/5209_2.png) [@N5NZZ](https://community.allstarlink.org/u/N5NZZ)\
**Post date:** [November 14, 2026, 10:49pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/8 "2026-11-14T22:49:13Z")

</div>

Just exactly how do you include the “yada yada” in the brackets .. and what where are these brackets? Why wasn’t this included in the install script?

.. we need to see the line by line command line sequence, straight up (aka “see John run”) style.

BTW I’m a coder, but not at all an html’er

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 11:27pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/9 "2026-11-14T23:27:37Z")

</div>

> [@KK6QMS](#):
>
> Is there a way to locate and verify the web ui is installed properly?

Is this an ASL3 Appliance or just running ASL3 on a Debian install? What's the output of `dpkg -l | grep asl`?

---

<div class="post-metadata">

**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\
**Post date:** [November 14, 2026, 11:29pm UTC](https://community.allstarlink.org/t/asl-web-ui-not-loading/25190/10 "2026-11-14T23:29:10Z")

</div>

> [@N5NZZ](#):
>
> Just exactly how do you include the “yada yada” in the brackets .. and what where are these brackets? Why wasn’t this included in the install script?
> 
> .. we need to see the line by line command line sequence, straight up (aka “see John run”) style.

The assumption is that people who have manually switched over to Nginx know what they're doing. All of the appliance-systems and default behavior is centered around Apache. Apache is very novice-friendly with configuration. Nginx is more complex. That's why the default system is Apache for ASL systems.
