Discussion - Trafiek fails to deploy - issue with ports available for portainer | PlexGuide.com

Discussion Trafiek fails to deploy - issue with ports available for portainer

  • Stop using Chrome! Download the Brave Browser via >>> [Brave.com]
    It's a forked version of Chrome with native ad-blockers and Google's spyware stripped out! Download for Mac, Windows, Android, and Linux!
Welcome to the PlexGuide.com
Serving the Community since 2016!
Register Now


Original poster
Feb 14, 2019
I recently had an issue with my server after an apt upgrade/update yielded some errors. I sorted those errors but left me with 513 errors, saying that my server was no reachable.
I rebooted and the 513 errors went away. Most apps work - Plex and *arr and nzbget all work fine (which is a relief), however xteve and portainer do not load; producing 404 errors.

When I try sudo pg I get told that Trafiek is not deployed properly. When I deploy I get this error:

TASK [Deploying portainer] ******************************************************************************************************************
Monday 02 March 2020 19:10:17 +0100 (0:00:00.027) 0:00:03.486 **********
fatal: []: FAILED! => {"changed": false, "msg": "Error starting container 43ae2c9669740fa52943241acc5f3ff38494e2cc4bfd74bce38d9a3be14fc361: 500 Server Error: Internal Server Error (\"driver failed programming external connectivity on endpoint portainer (ee18df8139460a0a00617648b7d66e5390d7fb5d030ad1b919b5b118915f980e): Bind for failed: port is already allocated\")"}
to retry, use: --limit @/opt/coreapps/apps/portainer.retry

Portainer is set as top level domain app. Nothing else has changed since the failed update caused everything to crash and burn. Any idea how to free up the port other than rebooting again and hoping it's free?

Recommend NewsGroups

      Up To a 58% Discount!