Nick Wilkinson
Nick Wilkinson
@ThomasCr we can confirm there is an issue here with the updater fetching the latest version, to fix this rather than using ```portainer/portainer-ee:latest``` you using ```portainer/portainer-ee:2.33.1``` for example this will...
@ThomasCr This is indeed an issue we are working on, the above is just a workaround
Hi @kale1d0code, I can't reproduce this. Can you break down the steps that will allow me to attempt to reproduce this as close as your environment?
Thanks @hookenz I have raised this with the team. ```internal: FR-833```
Are you running via a reverse proxy? If so, make sure your timeouts are not cutting the connection
Hi @Salvora Are you using a Proxy? If so can you see if this works by bypassing it? When you say this happens off and on, is this the same...
Can you please send me a screenshot of your this Portainer Home environment screen that displays your environments?
Thanks for that @Salvora, LAXSS appears to be running an older version of Docker. Could you look to update this and report back?
@rubinho76 Can you please confirm your Portainer version and details regarding your environment
Hello @intelligent002 Thanks for raising this and I can also see this within my environment. I will raise this internally `internal: EE-7292`