Android App - Can't use local controller

Mobile
1

I have a local controller setup, and when connecting to it via the Android App, it connects, however the app shows almost no information, and I cannot actually control anything in the App. I’m using the controller behind an Nginx proxy using custom DNS.

The app logs in, but when I try to view any of the pages in the app, it just spins. Nginx logs from the proxy are showing several requests that should have been properly served based on the log entries, as they all show 200s.

2

Have you also configured Settings -> System -> Advanced -> Allowed Origins?

satty-2025-08-21_13:48:47

3

Yes, and I can successfully use the browser with the custom URL/origin.

1 Like
4

Have you checked from a computer to see what the result is?

1 Like
5

Yes, works fine everywhere except the app

1 Like
6

What is Nginx pointing to, specifically?

7

Here’s the relevant parts of the nginx config:

server {
  set $forward_scheme https;
  set $server         "local.UID_HERE.ddns.manage.alta.inc";
  set $port           443;

  resolver            10.1.0.5 10.1.0.6 ipv6=off;

  listen 80;
  listen [::]:80;

  listen 443 ssl;
  listen [::]:443 ssl;
  http2 on;

  server_name alc.domain.com;

  # Let's Encrypt SSL
  ssl_certificate /data/lecerts/live/domain.com/fullchain.pem;
  ssl_certificate_key /data/lecerts/live/domain.com/privkey.pem;

  # Force SSL
  include conf.d/include/force-ssl.conf;

  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;

  access_log /data/logs/alc_access.log combined;
  error_log /data/logs/alc_error.log error;

  location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;

    # Proxy!
    include conf.d/include/proxy.conf;
  }
}

Proxy.conf that actually does the proxy:

add_header       X-Served-By $host;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Scheme $scheme;
proxy_set_header X-Forwarded-Proto  $scheme;
proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP          $remote_addr;
proxy_pass       $forward_scheme://$server:$port$request_uri;
8

It’s been a while since I worked with NRP, nothing’s standing out to me. Could you share a screenshot of what you are seeing within the app?

And if you add it via the DDNS hostname, does it work as expected?

9

Here’s the screenshot:

image
image421×937 28.7 KB

Adding via ddns hostname works, however that won’t accomplish me being able to manage this remotely since I have several things running on this network that are public facing on 80/443.

10

Yes, fully understood. I just wanted to make sure that the service behind the proxy was functioning as expected so we’re not trying to troubleshoot a symptom rather than the root problem. I’ll see if I can reproduce this and get back to you.

11

After working with @Alta-Jeff and @Alta-MikeD , I was able to finally dig up the issue. It appears firewalld on my host running my proxy was not properly allowing traffic on IPv6, but it had AAAA records in my local DNS.

In order to get this working, I just had to add an HTTPS rule in firewalld for IPv6 like this:

firewall-cmd --add-service=https --family=ipv6
firewall-cmd --add-service=https --family=ipv6 --permanent

Thanks to the Alta team for working through this, and sorry to waste your time on something that was not really Alta related.

5 Likes
12

No problem! Thank you for your willingness and persistence.

No worries at all, I don’t view it as time wasted; I see a possible opportunity to improve the general reliability of the app for all, plus it’s now working for you.

4 Likes