Casadream_1
-
Posts
68 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Casadream_1
-
-
Hello,
The original topic is closed and it seems that no one is interested in the problem anymore.
ph0b0s101 and I have the problem which is persistent.
---------------------------------------------------------------------------------
Please, development community, consider this.
I just found something.
If I go to the applications tab and come back to the dasboard.
Everything works as before, I also see the disks.
If I don't go to the applications tab, the disks are not visible and the dashboard is frozen.
By going to the applications tab, the freeze does not systematically disappear.
For it to truly disappear you have to scroll in the app tab.
Then at this point there is no longer any freeze.
-
Yes, but I cannot recover the movies screen captures of the old message.
-
It seems that this only concerns 2 people and therefore it is not interesting.
It's a shame.
-
-
By going to the applications tab, the freeze does not systematically disappear.
For it to truly disappear you have to scroll in the app tab.
Then at this point there is no longer any freeze.
Please, development community, consider this.
-
Please, development community, consider this.
I just found something.
If I go to the applications tab and come back to the dasboard.
Everything works as before, I also see the disks.
If I don't go to the applications tab, the disks are not visible and the dashboard is frozen.
-
The problem is since 3 versions. 6.12.2, 6.12.3 and 6.12.4 I would like to find the functioning as before, the problem only manifests itself with Unraid. Services that require websocket work well, if I disable websocket the service does not work well, which shows that websocket works well with NPM except for unraid since a few versions.
I use NPM jc21
Thank you.
-
I have the problem with 6.12.3 and 6.12.4
6.12.2 work.
-
Avant, lorsque ça fonctionnait bien c'était la 6.12.2 (et toutes celles d'avant).
A partir de la 0.3 et 0.4 impossible, tout est mort en passant par Nginx dont le cache est désactivé, et websocket activé pourtant.
-
same problem 6.12.3 and 6.12.4
-
I have the same problem but enable websocket do not work.
-
Avez-vous le problème de cache sur le dashboard ?
Style les jauges du processeurs sont inactives au bout d'un certain temps.
Tout se fige. Je suis passé à la 6.12.4 hier, au reboot les jauges fonctionnaient, et puis ce matin plus rien (par reverse proxy).
Après en local ça fonctionne, mais avant en distant ça fonctionnait bien depuis des années.
J'ai désactivé le cache avec Nginx mais rien de mieux. Des utilisateurs sur le forum anglais ont aussi des soucis.
-
On 5/17/2023 at 5:10 PM, autumnwalker said:
Anyone using a reverse proxy and experincing this? I just flipped to Nginx Proxy Manager and experienced this again. Toggling "websockets support" immediately solved the problem in the Unraid dashboard for me.
I have Websocket on NPM but the problem is here
-
Same problem
-
6.12.2 problem fixed.
-
This is diag, thanks.osiris-diagnostics-20230623-1804.zip
The servers are Dell PowerEdge R320 and R520
-
I wait fix. RC8 Ok for me.
-
RC8 work fine ! Grrr
-
version 6.12.1 is totally broken, containers no longer respond, broken dashboard... I'm switching to rc8 to see because I had no problems. Please fix it. Thanks
-
The same on two servers !
-
unraid container loading too long for load
-
Last plugin update
unraid user scripts failed parsing crontab for user root: *[ssd] /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck
- 1
-
I have exactly the same problem following the update of the plugin recently, in 2023.
-
The support does not provide any help on this subject.
[Support] Catduck Templates
in Docker Containers
Posted
Hello,
In the old version (which I didn't know) there was the possibility of configuring the front-end with the theme, accents and other things. I saw that this option has been "moved" but I don't see where, because if I change the url https://sub.domaine.com/admin/site-settings to https://sub.domaine.com/admin/site (as it was before the new version) I have a 404. Why didn't the devs keep this front-end configuration ?
Regards