Nick Wilkinson
Nick Wilkinson
@intelligent002 Hi! Nothing at this stage but I have followed this up internally and the team have acknowledged the issue and are looking into it. There is no ETA at...
Hello @Joly0 I have looked into this and can't reproduce it. Is this happening in one environment which is the Portainer Server environment which is running on Swarm?
@Joly0 Are you running behind a reverse proxy? If so have you tried bypassing this to confirm the issue remains?
@Joly0 If you open the browser dev console and in the network tab, do you see any errors when loading the logging page?
@Joly0 Thanks, so we have narrowed it down to Traefik. Are you allowing websockets in your proxy settings for Portainer?
Thanks @mnixry we are looking into this, I'll report back with any updates. ```internal: R8S-592```
@nickiman @markusonwheels83 Can you look at your logs as well as the API calls in the browsers dev console and look for any errors?
Under your containers, click the logs button Also for the dev console Open Developer Tools press F12 or right-click on the page and select Inspect, then navigate to the Network...
@nickiman > Regarding clicking the logs button in containers: It´s impossible for me because, if you see the picture of the containers section in my first post you will see...
```Internal: BE-12435``` We are currently looking into this