[BUG] Inform URL rejected

[mulbc]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When trying to adopt an existing AP, I try to use the manual adoption method via:

set-inform http://{IP}:8080/inform

After issuing the command I execute info and see that the URL is Rejected:

UAP-AC-Pro-Gen2-BZ.6.6.55# info

Model:       UAP-AC-Pro-Gen2
Version:     6.6.55.15189
MAC Address: 78:8a:20:[xxx]
IP Address:  172.[xxx]
Hostname:    UAP-AC-Pro-Gen2
Uptime:      7914085 seconds
NTP:         Synchronized

Status:      Server Reject (http://[redacted]:8080/inform)

When I try curl, I see that I get a HTTP Error 400:

UAP-AC-Pro-Gen2-BZ.6.6.55# curl -v http://{IP}:8080/inform
> GET /inform HTTP/1.1
> Host: 172.16.1.103:8080
> User-Agent: curl/8.4.0
> Accept: */*
> 
< HTTP/1.1 400 
< Content-Length: 0
< Date: Wed, 20 Mar 2024 16:28:48 GMT
< Connection: close
< 

I observe the same behavior on another computer and from within the container.

Needless to say - the AP is not discovered in the Unifi Console

Expected Behavior

The status does not show rejected and the console will allow adoption of the AP

Steps To Reproduce

1. Default install - no config needed

Environment

- OS: Fedora 39
- How docker service was installed: Podman from Fedora

CPU architecture

x86-64

Docker creation

podman run \        
  -d \
  --name=unifi-network-application \
  -e PUID=1000 \                    
  -e PGID=1000 \                                                               
  -e TZ=Europe/Berlin \     
  -e MONGO_USER=unifi \                        
  -e MONGO_PASS=[redacted] \
  -e MONGO_HOST=unifi-db \
  -e MONGO_PORT=27017 \  
  -e MONGO_DBNAME=unifi \
  -p 8443:8443 \
  -p 3478:3478/udp \
  -p 10001:10001/udp \
  -p 8080:8080 \
  -p 1900:1900/udp `#optional` \
  -p 8843:8843 `#optional` \
  -p 8880:8880 `#optional` \
  -p 6789:6789 `#optional` \
  -p 5514:5514/udp `#optional` \
  -v /srv/unifi:/config:Z \
  --restart unless-stopped \
  --label "io.containers.autoupdate=registry" \
  --network cblum_default \
  lscr.io/linuxserver/unifi-network-application:latest

Container logs

#  podman logs unifi-network-application                         
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[drizuid]

often, assuming correct info and mapped ports, you just need a factory reset. However, in your cased, based on

UAP-AC-Pro-Gen2-BZ.6.6.55# curl -v http://{IP}:8080/inform

GET /inform HTTP/1.1
Host: 172.16.1.103:8080

it looks like you are inputting the container ip in your inform address when it should be the docker host ip. Please confirm that you are NOT using the docker container ip, which your access point would not normally have knowledge of. Additionally, if you are using 172.16 as your LAN subnet you will want to ensure your docker bridge is not conflicting with it.

Finally, we do not support or test podman and we definitely do not support rootless.