You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed the archive box from portainer but the console kept failing to connect.
After some trial and error, I realized that all the containers I had installed were failing to connect to the console, which made me suspicious that the problem was with portainer itself.
Now that I think about it, most of the installations I've done in portainer that don't work with stack have been with task scheduler. Something made me suspect that there was something fundamentally wrong with portainer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Ask a Question!
I installed the archive box from portainer but the console kept failing to connect.
After some trial and error, I realized that all the containers I had installed were failing to connect to the console, which made me suspicious that the problem was with portainer itself.
Now that I think about it, most of the installations I've done in portainer that don't work with stack have been with task scheduler. Something made me suspect that there was something fundamentally wrong with portainer.
I followed the marius 30 second install guide for the portainer installation. (https://mariushosting.com/synology-30-second-portainer-install-using-task-scheduler-docker/)
I attatch the logfile of portainer and hope you guys can help me.
-> https://gofile.me/7brsP/NprQo9U2u
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions