Gbit Tech (818) 809-6743 SIGHT
C-7 #1050088  ·  Liability insured  ·  UniFi Certified PartnerNever the cheapest. Built to last.

UniFi Lab 10 Device shell: set-inform

Access point: not showing up

A brand new access point never shows up

Get the new access point to show up so you can it.

Not sure where to start? Check the firewall rule from Staging to the console (TCP 8080).

gateway with zone firewall and Cloud Key Gen2 Plus network host at 192.168.1.10. New AP on Staging VLAN 50 cannot reach TCP 8080, so it never shows up.LAB 10Device shell set-informGATEWAY + NETWORK HOST 0.8 px/mmGatewayZone firewallCloudKey192.168.1.10STAGING VLAN 50AP1.50.23Laptop1TERMINAL$ set-informhttp://192.168.1.10 :8080/informTCP 8080 to console: blocked.No devices waiting.TCP 8080 to console: allowed.

Run: Break A, Port 8080 blocked · factory default yes · TCP 8080 to host blocked · Staging to Internal block

AP adoption

No inform URL yet

Goal: Inform set, device Pending

Terminal Firewall

U7 Pro and the path

Front view · schematic link
U7 Pro front face. The inner ring around the U logo is steady white. U7 Pro front face. The inner ring around the U logo is steady blue. LED not modeled
Steady whiteReady for adoption

Simulation. A and B are schematic endpoints, not port positions. The cable shows your lab path, not proof of connectivity or adoption.

Sources and confidence for this art

Why this matters

Separate LED from list state.

Steady white means ready for adoption.

It does not prove the host is reachable.

Use the terminal to inspect the path.

Observe before fix

Read device status before changing a rule.

UniFi Devices

0 devices
No devices waitingThe AP has not been told where the Network host is.

Laptop terminal

Tech laptop · Staging VLAN 50Simulation · community-modeled output
laptop

# Laptop on Staging. New AP at 192.168.50.23 (example address).

# Tap a command below, or type one. Tab completes. Up repeats.

This terminal is a simulation, a lab mock modeled on community posts. Ubiquiti does not document the device shell or its info output. The prompt ui@U7-Pro:~# is an example prompt, and 192.168.50.23 and 192.168.1.10 are example addresses. After adoption, the login is the site's Device SSH Authentication credentials.

UniFi Network

CloudKey · LAN (Default) · 192.168.1.10

Adoption path AP to host

CheckNow
SSH loginNot connectedNeed: ui / ui
Factory defaultYesNeed: Yes
Inform URLNot setNeed: http://192.168.1.10:8080/inform
TCP 8080 to hostBlockedNeed: Open (host only)
Staging to InternalBlockNeed: Block
UniFi DevicesEmptyNeed: Pending Adoption

Controls

Firewall · Zone-Based

Allow TCP 8080 to 192.168.1.10

Staging to Internal · TCP 8080 · 192.168.1.10 only

Narrow exception. The port the AP informs on.

Allow Staging to Internal (all)

Staging to Internal · any port · any host

Wrong move. Opens the whole LAN to Staging.

Staging to Internal

Zone policy · everything else

Block

Staging to Internal: Block, TCP 8080 to 192.168.1.10 blocked

New AP

AP
192.168.50.23 · Staging 50
Factory default
Yes · LED steady white

Only matters if the AP was adopted before.

Other ways to inform · info only

Out of scope for this lab

STUN troubleshooting Community SSH reset Backup restore walkthrough Console root SSH SSH keys Firmware upgrade Linux shell File edits and logs Protect adoption · Lab 05

Gear in this lab

  • 1 Network host (CloudKey)
  • 1 Gateway (Zone-Based Firewall)
  • 1 New AP (factory default)
  • 1 Tech laptop
Change on win: none yet

Config only. The fix needs no new hardware. Counts only, no prices.

Pending Adoption

Managed by Other

set-inform

A teaching lab, not a quote and not a design for your site. Settings are simplified from the UniFi Network app. Device shell output is a lab mock, not real device output. No account, and nothing from this lab is saved.