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
When trying to connect to the console of a running container, after clicking Connect the error message Forbidden - CSRF token invalid gets displayed. The connection to the console cannot be established.
Steps to reproduce the issue:
Click on the Console link on a running container
Click on the Connect button
When inspecting the failed request in the DevTools I see the request to
Target Docker version (the host/cluster you manage): 1.12.3
Platform (windows/linux): Elementary OS (Loki, Ubuntu 16.04)
Browser: Chromium 54
The text was updated successfully, but these errors were encountered:
tobias-kuendig
changed the title
Forbidden - CSRF token invalid when trying to connecto to consoleForbidden - CSRF token invalid when trying to connec to console
Nov 2, 2016
This bug seems related to the current CSRF protection implementation... which in my opinion is flawed so I'm probably going to disable it for now and review it in the future.
deviantony
changed the title
Forbidden - CSRF token invalid when trying to connec to consoleForbidden - CSRF token invalid when trying to connect to console
Nov 3, 2016
@tobias-kuendig a workaround for this problem at the moment is to clear your browser cookies for your domain (e.g. localhost:9000 or portainer.mydomain). This will allow you to retrieve a valid CSRF token on the next request to Portainer and will prevent this issue to arise.
… the storage option is disabled on cluster (#310)
* fix update application with persisted data
* revert
* revert
Co-authored-by: Maxime Bajeux <max.bajeux@gmail.com>
Description
When trying to connect to the console of a running container, after clicking
Connect
the error messageForbidden - CSRF token invalid
gets displayed. The connection to the console cannot be established.Steps to reproduce the issue:
Console
link on a running containerConnect
buttonWhen inspecting the failed request in the DevTools I see the request to
fails with a
403 (Forbidden)
error.The response of the failed request is
CURL of the failed request
Technical details:
The text was updated successfully, but these errors were encountered: