Container sabnzbd - err_connection_refused after new image pull

[pm317b]

Have had sabnzbd running for about a year as a container and have updated previously with no issues. Updated the image today as some regular maintenance and getting "err_connection_refused" when attempting to connect via local network (192.168.xx.xx:8080). Troubleshooting steps:

- Checked the host firewall to ensure that rules did not change
- Ubuntu host, sudo ufw status = inactive
- Checked other containers, all running fine and connect fine
- Checked listening ports on host vm - port 8080 is showing listening by docker service.
- On host checked docker container ls - it shows that sabnzbd is running and is monitoring for traffic on 8080 (matching above)
- Connected to shell of sabnzbd - logs show service shutdown at time the container was stopped but do not show a service restart
- unsure if that is normal

I have repulled the image a few times to no avail. A bit uncertain how to proceed. Anybody have an idea?

[pm317b]

Found the issue - posting here for fruition. In the Docker logs it stated that some of the requirements were missing - specifically sabctools. Took a look at github repository for the image and found that Portainer has been cloning environment variables from old versions to the new version. Pulled down the container and removed all defined environment variables and relaunched the container. Issue resolved.

Thanks a lot Portainer. *old man yelling at the sky*