# Discovery without Cloud

There could be reasons cloud discovery does not complete. These include:

* Lack of Internet Connectivity
  * Device may require additional WAN settings
  * Network may not be connected to Internet
* No Configuration of Cloud in Certificate Authority
  * Manufacturer may have left this value blank in the device record stored in Certificate Authority

![Manual Cloud Entry](https://1686450113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfA93RxblNlIBkzfMWezd%2Fuploads%2Fgit-blob-9a83ab810cf180893692f2d1bde36d1266cb218f%2Fimage%20\(23\).png?alt=media)

When the cloud can not be automatically discovered, OpenWiFi devices will turn on a local admin web UI made available via SSID "Maverick".

The Maverick UI will support configuring WAN interface parameters, including DHCP, Static, PPPoE, and LTE/5G settings. Please see [Local Device Settings](https://tip-1.gitbook.io/openwifi/2.9.0/openwifi-stack/access-points/local-device-settings) for details on using Maverick.[<br>](https://tip-1.gitbook.io/openwifi/2.9.0/openwifi-stack/access-points/local-device-settings)Additionally the Maverick UI supports direct entry of the cloud for cases when the cloud value has not been supplied during manufacture.

For non-Wi-Fi devices such as PoE access switches, the same cloud location information may be configured using local management interface.

![Admin / User Entered WAN or Cloud](https://1686450113-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfA93RxblNlIBkzfMWezd%2Fuploads%2Fgit-blob-b96313e8aa91fb0f7857a80c3c33676d44c600b0%2Fimage%20\(24\).png?alt=media)
