Http status error on starting up neurodesk when running as a container in Docker #425
Replies: 3 comments 1 reply
-
dear @StephWithey that’s a bug that occurs when a Neurodesktop session wasn’t shutdown and crashed. We are working on a solution so that a restart of the neurodeskapp fixes it. for now, you have 2 ways of fixing it:
@iishiishii that’s the bug that’s needs clearing of the Neurodesk app caches |
Beta Was this translation helpful? Give feedback.
-
@stebo85, thanks so much for the quick reply. I cleared the cache and it is now working again. |
Beta Was this translation helpful? Give feedback.
-
this bug is now fixed and the cache is cleared automatically. |
Beta Was this translation helpful? Give feedback.
-
I have been running Neurodesk as a container in Docker with no problems until just over a week ago when the following error popped up on launching Neurodesk locally. An internet search suggests increasing the maxHTTPheadersize in Apache Tomcat which I have tried to do. But the error is still coming up.
![error_neurodesk](https://private-user-images.githubusercontent.com/42540370/342970702-abc8005c-e9c5-496c-93d2-31e05801629c.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkzMTkyMjEsIm5iZiI6MTczOTMxODkyMSwicGF0aCI6Ii80MjU0MDM3MC8zNDI5NzA3MDItYWJjODAwNWMtZTljNS00OTZjLTkzZDItMzFlMDU4MDE2MjljLlBORz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEyVDAwMDg0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRiNjU2MDZiZjkxYmJjYWQ2NTlhZmQyZjAwYWZmOGZmMGVmZmQ2MDVjNGFhNDViMTE5ZTA1MjY0NWQwYzYwZGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.AVnwWgYhHOI1zKJK1errxrtjb8-0bEFVhQh83L6OiKE)
Any suggestions, please? Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions