[[Support] omada-controller]

1 minute ago, flyize said:

No, the default template is wrong. It has directories that are some weird path like /mnt/extrassds or something. That is not a valid path.

Good deal. I figured I had something screwed up. 👍🏻

[[Support] omada-controller]

On 8/6/2023 at 8:56 AM, flyize said:

I just (re)installed 

It looks like this is because OP left his non-standard pathing in there for the data/log/etc.

I ended up buying a hardware controller and removing this from my server. But I’m still curious as to what I may have done wrong. Are you saying I setup the template wrong?

[[Support] omada-controller]

On 7/24/2023 at 8:28 PM, MaxAbsorbency said:

 

Check your MANAGE_HTTP_PORT / MANAGE_HTTPS_PORT variables on the omada-controller container and make sure that's the port you're connecting to (http:// or https:// respectively)

they are the default values of 18043 for https and 18088 for http.  when I click the webui button it opens https://192.168.10.5:18043/login , which is correct.  however, I get a "cannot connect to server" error page.  its odd for sure as all of my other apps are perfectly accessible.

[[Support] omada-controller]

Ok, gonna show what is quite possibly my stupidity here. I’ve installed the container with default template, I didn’t change anything. When I try to go to the webui, I get a “cannot connect to server”. Did I miss some required change to the template or something else perhaps. Also, after some time the container appears to be stopping itself. I’ve removed and redownloaded once already with no fix. Any ideas? Thanks in advance.