i just noticed while trying to get fail2ban working (damn hard btw.. I could really use some help with fail2ban to work with authelia and nginx.. with docker)

 

There is a red dot showing the error: incorrect autostart order.. 

i dont know where i can check what the order should be then... 

 

this is my list as it is right now:

mariadb

redis

fail2ban

adguard-home

nginx

authelia

unifi-controller

adguard-sync

nextcloud

*arrs and downloaders

I have this as well, though it used to be a rocket ship icon I think

I was about to post the same question so was surprised to find it had been asked only a few hours ago.

 

I did a bit more digging and found the following information on this page: 

 

Relevant section:

 

Quote

 

AUTOSTART

 

With this plugin installed, you have to keep in mind that the order of the containers/vm might not be the actual order of the container, this is an issue with containers that are set to autostart.

The plugin checks what you see and the unraid order and shows if the order is the same with this icon .

If this icon is green like here means that the order you see is the same of unraid, if the icon is red this means that the unraid order is different.

To fix that you can simply reorder a folder or a container and then refresh the page, you will see that the icon is turned green.

 

 

I reordered a couple of containers, refreshed the page, and I'm now back to a green icon with "Correct autostart order". Hope this solves yours.

 

3 hours ago, Gunny said:

I have this as well, though it used to be a rocket ship icon I think

Yeah, sorry about that, I forgot to mention in the forum, but I put it in the changelog for the plugin, I changed it while testing, and at the end I stuck to it.

 

4 hours ago, furian said:

i just noticed while trying to get fail2ban working (damn hard btw.. I could really use some help with fail2ban to work with authelia and nginx.. with docker)

 

There is a red dot showing the error: incorrect autostart order.. 

i dont know where i can check what the order should be then... 

 

this is my list as it is right now:

mariadb

redis

fail2ban

adguard-home

nginx

authelia

unifi-controller

adguard-sync

nextcloud

*arrs and downloaders

To resolve this you simply reorder at lest one container in the docker tab and then refresh, after that you should see it green.

I reordered some and it still says the autostart is out of order.

On 10/16/2023 at 7:31 PM, bobbintb said:

I reordered some and it still says the autostart is out of order.

 

Same with me.

Same here... is there any easy way to determine what the start order *should* be?

 

On 10/20/2023 at 5:03 AM, DrBazUK said:

Same here... is there any easy way to determine what the start order *should* be?

 

Same here... as well as understanding what the effect will be if the autostart is out of order?

Edit: Followed the instructions in this post to fix it:

https://forums.unraid.net/topic/142782-plugin-folderview/?do=findComment&comment=1317005

 

Edited October 22, 20232 yr by exoexo

Here is my answer, if you need any help with my plugin please post there, I tend to be more active there because I have notification active for that thread.

@exoexo @bobbintb please check 

 

SOLVED:

1. click on padlock to unlock changes in Docker folders.

2. Drag one folder to a new position.

3. Drag it back to the previous position.

4. Click padlock to lock it

 

Result - no more error on folder view.

So, no matter what I do I can't fix this ... The pentagon will turn green for a split second than go back to red.

 

Is there something else I'm missing ?

Edited February 16, 20242 yr by bombsngravyb1

22 minutes ago, bombsngravyb1 said:

So, no matter what I do I can't fix this ... The pentagon will turn green for a split second than go back to red.

 

Is there something else I'm missing ?

 

On 10/22/2023 at 7:25 PM, scolcipitato said:

Here is my answer, if you need any help with my plugin please post there, I tend to be more active there because I have notification active for that thread.

 

On 10/16/2023 at 11:31 AM, bobbintb said:

I reordered some and it still says the autostart is out of order.

 

On 10/19/2023 at 2:21 AM, jpslv said:

 

Same with me.

 

On 10/20/2023 at 4:03 AM, DrBazUK said:

Same here... is there any easy way to determine what the start order *should* be?

 

I was able to remove the container from the folder, move it below that folder (so it changes the unraid start order) then add it back to the folder. 

What's the benefit of having the symbol green? or are we all just chasing a color here?

On 10/12/2023 at 12:33 PM, scolcipitato said:

Yeah, sorry about that, I forgot to mention in the forum, but I put it in the changelog for the plugin, I changed it while testing, and at the end I stuck to it.

 

To resolve this you simply reorder at lest one container in the docker tab and then refresh, after that you should see it green.

Thank you! This worked perfectly once I unlocked the Dockers page with the "lock" icon next to the red out of order icon.

On 12/3/2024 at 7:38 PM, MightyRufo said:

What's the benefit of having the symbol green? or are we all just chasing a color here?

Docker Services can rely on each other.

For example paperless-ngx relies on redis.

If the start order is incorrect, paperless-ngx may not start correctly and/or exits with as failed.

Think of a docker-compose file where the services are structured / orchestrated to work hand in hand.

Also from my experience with unRAID: Having an incorrect start order may crash your docker system (and can take your VM system with it).