#OMADA SDN - Can't access web interface after install
15 messages · Page 1 of 1 (latest)
Hi, yea it wasnt shown in the screenshots but I was on the correct port. I guess I will give it a 3rd shot as other people seem to have had similar issues that just magically vanished by reinstalling over and over
I now reinstalled in Verbose mode and it showed this which it didnt before in normal mode:
I was wondering if that mightve been the problem, but as a newbie im too stupid to figure out how I'd be able to install it with an older Mongo (i think 4.4 is needed)
We have cancel the Support for Mongo 4.4 because its deprecated since ages and an Security risk
well... lets say im willing to take a risk as my CPU doesnt support AVX and i really dont want to buy a whole new system.
would there be a way?
Just grab a docker container instead of an LXC?
what difference would that make in solving my issue?
the LXC script works on latest, for docker containers you can grab the last known 5.x version that still has mongo 4.x
It won't get any more updates but it will work on your hardware at least
hm. i guess i gotta look further into that.
thanks good sir.
I personally use https://github.com/mbentley/docker-omada-controller the latest non-RC release is still mongo 4.4 FYI
Maybe i Check it in next 2 or 3 weeks again, If the new core is pushed into live
yea there is no way im getting that to work without having the slightest idea about any of this 😄
thanks tho
https://gist.github.com/ssagga/bc4d3fc8c150cb66d9cadd082a2b6806
i found this which seemed really promising.
however now im stuck at the last step and i get this:
dpkg: error: cannot access archive 'Omada_SDN_Controller_v5.x.y.z_Linux_x64.deb': No such file or directory
any ideas?