-
|
Things seemed to be going well for a while but I am now locked out again from my cloud. I'm not sure what has caused it now, with no further changes having been made to my set up to my knowledge. I have killed all containers and pruned them plus the networks. However, when I attempt to load my host machine at https://tiddles.local:8080 I am presented with a two minute wait before being presented with the containers page. Clicking "start and update containers" however does nothing, it has become utterly unresponsive. Here are the logs in question, note the 2.5 minute gap between the page being requested and actually being served. The line of interest I would suggest would be: |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 19 replies
-
|
Hello, thanks for your report! Can you please see if these steps works for you and fix the problem? |
Beta Was this translation helpful? Give feedback.
-
|
This was unfortunately a bug for new instances in 1.2.1 which should be fixed with 1.3.0 but only for new instances, hence this workaround was provided. |
Beta Was this translation helpful? Give feedback.
-
|
I've attempted to take those steps (after a reboot and attempt to prune all things several times, the containers in question aren't running anyway) but I'm getting no change in behaviour, with the 2.5 minute wait still remaining for the containers to load and the Start button being unresponsive. |
Beta Was this translation helpful? Give feedback.
-
|
Could I get a specific github branch some how in my docker compose file by changing the line |
Beta Was this translation helpful? Give feedback.
-
|
1.3.0 was just released |
Beta Was this translation helpful? Give feedback.
-
|
But if your mastercontainer cannot reach the internet, you may need to stop it, delete it and recreated it using the same command that you initially used. Can you post the output of |
Beta Was this translation helpful? Give feedback.
-
|
Can you please follow these steps again and see if it helps? |
Beta Was this translation helpful? Give feedback.
-
|
Nope. And I've tried many times now. |
Beta Was this translation helpful? Give feedback.
-
|
I've commented out all the other containers just to see if they might have been conflicting with it, but much the same thing happens, and it all freezes up for four minutes or so after the first two lines it spits out. |
Beta Was this translation helpful? Give feedback.
-
|
Can you post your docker-compose file? Seems like you added the mastercontainer to a network? |
Beta Was this translation helpful? Give feedback.
-
|
I certainly didn't mean to, but I do wonder where this "apbarratt_default" keeps coming from. I'd just assumed it was something docker always creates by default: This is it in its current state with stuff commented out for testing but even then still acting off :/ |
Beta Was this translation helpful? Give feedback.
-
|
I've managed to trick the containers into starting by manually submitting the form in question using the console. After the required 2.5 minute wait it came up with a 405 method not allowed message but the containers were indeed started. |
Beta Was this translation helpful? Give feedback.
-
|
I’ve figured it out! Or rather, I’ve figured out the cause of the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Curiously, the maps integration issue I was having is now even worse, in fact, the integrations page just doesn't load at all anymore, just showing a blank white container with the Nextcloud navigation bars around it. |
Beta Was this translation helpful? Give feedback.
I’ve figured it out! Or rather, I’ve figured out the cause of the issue.
If you remember in my struggles with setup, I decided to give my machine its own fixed IP address by subscribing to a VPN (PureVPN). This is connected using PPP by running the command
sudo pon purevpn. It occurred to me that the main cloud seemed to be connecting quickly enough (when it’s running, though buggy at points, the weather still doesn’t load and I still cannot install apps) but only the AIO admin console was moving so cripplingly slowly with its constant 2.5 minute wait times.Well, I was trying to figure out what had changed during all my tinkering when the slow down started and that was it.
So I went to c…