taprackpew Posted July 27, 2023 Share Posted July 27, 2023 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. Quote Link to comment
mbentley Posted July 27, 2023 Share Posted July 27, 2023 (edited) On 7/26/2023 at 10:19 PM, taprackpew said: 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. I am not as familiar with the interface for starting a container but just make sure that the ports exposed AND the environment variables that you used to launch the container match. If you have previously launched the container with different ports, you can't just change them due to how the controller software is written. Take a look at this part of the readme if you want to fully understand but the env vars modify a properties file which is only read on the very first startup by default. Edited July 28, 2023 by mbentley link didn't work Quote Link to comment
flyize Posted August 6, 2023 Share Posted August 6, 2023 I just (re)installed On 7/26/2023 at 10:19 PM, taprackpew said: 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. It looks like this is because OP left his non-standard pathing in there for the data/log/etc. Quote Link to comment
taprackpew Posted August 7, 2023 Share Posted August 7, 2023 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? Quote Link to comment
flyize Posted August 7, 2023 Share Posted August 7, 2023 4 hours ago, taprackpew said: 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? 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. Quote Link to comment
taprackpew Posted August 7, 2023 Share Posted August 7, 2023 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. 👍🏻 Quote Link to comment
BurntOC Posted August 29, 2023 Share Posted August 29, 2023 (edited) Hi all, revisiting this after some successful tests a couple years back. I'm ready to migrate from Unifi and I've gotten one of my two new switches adopted, though I did enable cloud access to do that. I'd strongly prefer NOT to enable cloud access, so now that I've disabled it I cannot for the life of me get the controller to show the second switch I want to adopt. The controller and the switches are on different subnets and VLANs, but I believe the port for the container (Unraid GUEST interface VLAN/net) and the switch (INFRA VLAN/net) have the PVID and tagged VLANs set properly, and I can ping back and forth both ways. I also have all the 29810-29816 ranges,18043, 27001 (and actually just all the dang high ports for now) opened between the two on the firewall. Lastly, I've gone into the new switch interface and told it the IP of the controller. All that done and I just cannot get it to show. I figure many of you are running standalone with cloud access disabled. Any advice on how I can resolve this? Edited August 29, 2023 by BurntOC Quote Link to comment
mbentley Posted August 31, 2023 Share Posted August 31, 2023 On 8/29/2023 at 2:11 PM, BurntOC said: I figure many of you are running standalone with cloud access disabled. Any advice on how I can resolve this? I would suggest posting to the TP-Link support forums since this isn't a massive group of experts on the software itself. Quote Link to comment
BurntOC Posted September 18, 2023 Share Posted September 18, 2023 Got it working, thanks. Quote Link to comment
LotF Posted September 25, 2023 Share Posted September 25, 2023 Since an update today I cannot log into the controller anymore. Does anybody else have that problem? I am very sure that I am using the correct credentials. Quote Link to comment
mbentley Posted September 26, 2023 Share Posted September 26, 2023 (edited) 20 hours ago, LotF said: Since an update today I cannot log into the controller anymore. Does anybody else have that problem? I am very sure that I am using the correct credentials. Yes, others are reporting the same. I created an issue on the TP-Link forums: https://community.tp-link.com/en/business/forum/topic/623942?replyId=1258164 and there is a discussion tracking it on the image GitHub: https://github.com/mbentley/docker-omada-controller/issues/342. People are also posting about it on Reddit: https://www.reddit.com/r/TPLink_Omada/comments/16rb07h/admin_login_doesnt_work_after_updating_to_latest/ It doesn't seem to be happening to everyone though so that's the odd part. Edited September 26, 2023 by mbentley Quote Link to comment
ibphantom Posted October 14, 2023 Share Posted October 14, 2023 The container is broken for me " text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file... text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file... Quote Link to comment
mbentley Posted October 15, 2023 Share Posted October 15, 2023 4 hours ago, ibphantom said: The container is broken for me " text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file... text error warn system array login tar: html/Omada.png: Cannot write: No space left on device tar: html/echarts.min.js: Cannot write: No space left on device tar: html/logo.png: Cannot write: No space left on device tar: Exiting with failure status due to previous errors /entrypoint.sh: line 301: echo: write error: No space left on device INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) doesn't exist; creating INFO: User (omada) doesn't exist; creating INFO: Time zone set to 'America/Los_Angeles' INFO: Setting 'manage.http.port' to 18088 in omada.properties INFO: Setting 'manage.https.port' to 18043 in omada.properties INFO: Setting 'portal.http.port' to 18088 in omada.properties INFO: Setting 'portal.https.port' to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report HTML directory missing; extracting backup to '/opt/tplink/EAPController/data/html' html/ html/Omada.png html/echarts.min.js html/logo.png INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508) INFO: Group (omada) exists; skipping creation INFO: User (omada) exists; skipping creation INFO: Time zone set to 'America/Los_Angeles' INFO: Value of 'manage.http.port' already set to 18088 in omada.properties INFO: Value of 'manage.https.port' already set to 18043 in omada.properties INFO: Value of 'portal.http.port' already set to 18088 in omada.properties INFO: Value of 'portal.https.port' already set to 18843 in omada.properties INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties INFO: Value of 'port.discovery' already set to 29810 in omada.properties INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties INFO: Value of 'port.rtty' already set to 29816 in omada.properties INFO: Report PDF directory missing; creating '/opt/tplink/EAPController/data/pdf' WARN: Ownership not set correctly on '/opt/tplink/EAPController/data'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/logs'; setting correct ownership (omada:omada) WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada) INFO: Database directory missing; creating '/opt/tplink/EAPController/data/db' done INFO: Version check passed; image version (5.12.7) >= the last version ran (0.0.0); writing image version to last ran file... You’re out of disk space wherever it is trying to write to. Errors specifically call that out. 1 Quote Link to comment
ibphantom Posted October 15, 2023 Share Posted October 15, 2023 (edited) 12 hours ago, mbentley said: You’re out of disk space wherever it is trying to write to. Errors specifically call that out. I've never had a problem with the container before this previous Major update. The error was fixed by changing /mnt/disks/user/docker-settings/omada-controller/ instead of /mnt/disks/extrassd/ This error started when 5.12.X came out. My last backups of this are from 5.9.31 and it's still giving me this even if I try to pull the 5.9.x Tag @mbentley New Error after changing to /mnt/disks/user 2023-10-15 07:28:24,380 Log4j2-TF-5-AsyncLoggerConfig-4 ERROR An exception occurred processing Appender RollingFile org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to stream ../logs/server.log at org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:252) at org.apache.logging.log4j.core.appender.FileManager.writeToDestination(FileManager.java:277) at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.writeToDestination(RollingFileManager.java:275) at org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:283) at org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:294) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:199) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:190) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:181) at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:312) at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:542) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.callAppenders(AsyncLoggerConfig.java:126) at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:500) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:483) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.log(AsyncLoggerConfig.java:120) at org.apache.logging.log4j.core.async.AsyncLoggerConfig.logToAsyncLoggerConfigsOnCurrentThread(AsyncLoggerConfig.java:168) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:112) at org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:98) at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.io.IOException: No space left on device at java.base/java.io.FileOutputStream.writeBytes(Native Method) at java.base/java.io.FileOutputStream.write(FileOutputStream.java:349) at org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:250) ... 23 more Edited October 15, 2023 by ibphantom Quote Link to comment
hedrinbc Posted October 15, 2023 Author Share Posted October 15, 2023 (edited) @ibphantom Please check that all 3 file paths (Host Path 1, 2, 3) map to working shares on your machine. There is a seperate "logs" share name posibly this is set incorrectly. No idea how this would have worked prior without them set to working shares on your machine. Edited October 15, 2023 by hedrinbc Quote Link to comment
ibphantom Posted October 16, 2023 Share Posted October 16, 2023 6 hours ago, hedrinbc said: @ibphantom Please check that all 3 file paths (Host Path 1, 2, 3) map to working shares on your machine. There is a seperate "logs" share name posibly this is set incorrectly. No idea how this would have worked prior without them set to working shares on your machine. I've tried. Nothing should have changed, but when I do change the Host Paths from /mnt/disks/user/docker-settings/omada-controller/ instead of /mnt/disks/extrassd/, that's when I get the second error. The first error occurs since the update to 5.12.X Quote Link to comment
present_absence Posted October 16, 2023 Share Posted October 16, 2023 9 hours ago, ibphantom said: The error was fixed by changing /mnt/disks/user/docker-settings/omada-controller/ instead of /mnt/disks/extrassd/ is that because extrassd is full but /user/docker-settings is on a share spanning other disks and is not full? your new error is also a failure to write to file, perhaps that location is still on a full disk Quote Link to comment
ibphantom Posted October 16, 2023 Share Posted October 16, 2023 Just now, MaxAbsorbency said: is that because extrassd is full but /user/docker-settings is on a share spanning other disks and is not full? your new error is also a failure to write to file, perhaps that location is still on a full disk I have 13TB Free and my docker file is double the normal in size, every other container works, and I've changed file permissions to 777. Still having the problem. Quote Link to comment
hedrinbc Posted October 16, 2023 Author Share Posted October 16, 2023 (edited) @ibphantom I don't know your situation but I believe "disks" is likely incorrect. This is a more standard path... /mnt/user/appdata/docker-settings/[app name] The original setting when you pulled down the template included my "extrassd" which was outside my array (unassigned disk) and could only be accessed through the path /mnt/disks/extrassd. It all matters how your system is set up to set paths. If you go into the console can "cd /mnt" "cd user" etc... You can see what are best paths for you. Edited October 16, 2023 by hedrinbc Quote Link to comment
dinomyte Posted November 3, 2023 Share Posted November 3, 2023 (edited) Hi all, does anybody else has issues after todays docker update? All devices are hanging in "Adopting" state 😰 Was everything working like a charm since weeks and after last updates... Br Dino Edit: seems like all Settings are vanished?? Edited November 3, 2023 by dinomyte Quote Link to comment
i1mran92 Posted November 3, 2023 Share Posted November 3, 2023 1 hour ago, dinomyte said: Hi all, does anybody else has issues after todays docker update? All devices are hanging in "Adopting" state 😰 Was everything working like a charm since weeks and after last updates... Br Dino Edit: seems like all Settings are vanished?? yeah. i'm having the same issue. main page showing general error as well Quote Link to comment
mbentley Posted November 3, 2023 Share Posted November 3, 2023 Sorry about that - an issue with a new experimental feature to allow users to make the MongoDB work from another container or host accidentally broke the connection to the MongoDB that the controller spins up. I forgot to add a default connection string but it should be fixed now. 2 Quote Link to comment
dinomyte Posted November 4, 2023 Share Posted November 4, 2023 (edited) Fixed! Thanks a lot for your fast support!!! Edited November 4, 2023 by dinomyte Quote Link to comment
warnie Posted November 4, 2023 Share Posted November 4, 2023 Unbelievable. thank you mbentley. I thought I was going crazy. I've literally trying to setup brand new switch this morning that arrived today and couldnt figure why it wouldnt adopt! Talk about timing. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.