Omada Software Controller captive portal setup
The software controller is the OC200 as an application on your own PC, NAS or server. Where you run it decides whether the portal works on the first try: on a back office PC it needs the same inbound path as a box, on a VPS it already has one.
Reviewed by Pierre Subeh, Founder, VoqadoWiFi · Written by the VoqadoWiFi team · Updated
https://www.voqadowifi.com/portal/your-venue-slug. Allow www.voqadowifi.com and voqadowifi.com before authentication, then give the controller a public HTTPS address with a trusted certificate, which a VPS behind a reverse proxy does naturally.At a glance
- Where it runs
- Your PC, NAS or a VPS
- Usual management port
- 8043 in the browser
- Port the token call uses
- The port in the saved address, 443 if none, with certificate checking
- Portal URL
https://www.voqadowifi.com/portal/your-venue-slug- Multi venue
- One controller, one Omada site per venue
- Path the token goes to
/<omadacId>/portal/authwhen Omada sendsomadacId
Checked against the VoqadoWiFi integration code on 7 October 2026. Controller menu labels move between firmware releases; the setting names above are the ones the setup wizard prints.
Step by step
- Pick where the controller livesA spare PC in the office works for a pilot. For anything you depend on, a small VPS is the stronger choice: it is reachable from the internet by design, and one controller can hold a site for every venue.
- Put a trusted certificate in front of itThe software controller usually answers on 8043 with a self signed certificate. The authorization call from VoqadoWiFi connects to the port in the address you save and checks the certificate. The tidy setup is a reverse proxy on 443 with a free automated certificate that forwards to the controller.
- Open the portal settings for the venue’s siteChoose the site from the site selector, then Settings, Authentication, Portal. Edit or create the portal bound to the guest SSID and choose External Portal Server.
- Paste the portal URL exactly as the dashboard prints itEnter
https://www.voqadowifi.com/portal/your-venue-slugwith no trailing slash and no question mark of your own. Omada appendsclientMac,apMac,ssidName,radioIdand a one timetokento the URL, and a second query string breaks that hand off. - Allow the portal domain before authenticationAdd
www.voqadowifi.comandvoqadowifi.comto Pre-Authentication Access on the same portal. The full list, with the reason for each line, is on the walled garden page. - Save the controller in the dashboardEnter the public
https://hostname as the Omada Controller URL, with the port if it is not 443, the Site ID, and the Controller ID shown asomadacIdin a redirect URL. Saving the Controller ID lets authorization work even when a redirect arrives without it. - Test one venue end to endJoin the guest SSID on a phone that has never connected, submit the form and confirm the device gets online. Check Portal Health for the matching attempt before you roll the same portal out to the next site.
What breaks on this controller
Leaving the port off the saved address
If the controller only answers on https://controller.example.com:8043 and you save it without :8043, the token call goes to 443 and reaches nothing. Portal Health shows a network failure. Save the address exactly as it opens in your browser, and make sure that port has a trusted certificate.
Redirects that arrive without omadacId
Current controllers include omadacId in the redirect, and the token goes to /<omadacId>/portal/auth on your host. If a redirect arrives without it, the integration falls back to the site based path or plain /portal/auth. Saving the Controller ID in the dashboard removes the guesswork.
The controller PC goes to sleep
A controller on a desktop that sleeps or restarts for updates takes guest authorization with it. Guests still see the portal, because the access points redirect on their own, and then never get online.
One site for several venues
Put each venue in its own Omada site. Portal settings, SSIDs and the Site ID VoqadoWiFi stores are per site, and sharing one site mixes guests across venues.
The VPS pattern for groups
Run one software controller on a VPS, create one Omada site per venue, and adopt each venue’s access points to it over the internet. Every VoqadoWiFi location then points at the same controller hostname with its own Site ID.
The reachability problem disappears, because the controller is on the internet already. What you take on is a server: operating system updates, controller updates, backups copied off the machine, and a test login per venue after every controller upgrade.
Questions
Which version of the software controller do I need?
Can I keep the controller on 8043?
:8043 so the authorization call uses that port, and give it a trusted certificate. A reverse proxy on 443 is tidier, because the management port then stays private.Do I need to open the controller to the whole internet?
Is the software controller free?
Deeper reading
Longer articles from the blog that cover this controller. Where an article and this page disagree, this page is the one checked against the current integration.
- TP-Link Omada setup hub. The three Omada controllers side by side.
- Running one controller on a VPS. Written for UniFi; the sizing, backup and update habits carry over.
- Guest bandwidth management
Keep reading
Sources: lib/omada/api.ts (buildAuthUrl and the token call) and the setup wizard, read on the date above. TP-Link and Omada are trademarks of TP-Link Technologies. VoqadoWiFi is not affiliated with or endorsed by either vendor.
Get the free Guest WiFi Launch Pack
Four worksheets for switching guest WiFi on at your venue: a network inventory, a launch acceptance checklist, a change window plan and a staff handoff. Works for Omada and UniFi setups.
Run your Omada portal free One location and 500 guest logins a month on the Starter plan, no card. The dashboard prints the finished portal URL for this controller. Create your free account