[GH-ISSUE #527] Changine Docker Port Breaks Web UI #1849

Closed
opened 2026-03-01 17:54:13 +03:00 by kerem · 3 comments
Owner

Originally created by @jmcree on GitHub (Nov 6, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/527

I'm on unraid and using the repository from nikisweeting/archivebox:latest

By default the docker uses port 8000. This is already taken on my system and when I try to change it to say port 5000, the webUI says it cannot reach this page. I have changed the port in the basic docker setting, specified the webUI url in the advanced docker settings to use port 5000 and told the server to run on 0.0.0.0:5000 in the console. What am I missing to get it to run on a different port?

Originally created by @jmcree on GitHub (Nov 6, 2020). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/527 I'm on unraid and using the repository from nikisweeting/archivebox:latest By default the docker uses port 8000. This is already taken on my system and when I try to change it to say port 5000, the webUI says it cannot reach this page. I have changed the port in the basic docker setting, specified the webUI url in the advanced docker settings to use port 5000 and told the server to run on 0.0.0.0:5000 in the console. What am I missing to get it to run on a different port?
kerem closed this issue 2026-03-01 17:54:14 +03:00
Author
Owner

@pirate commented on GitHub (Nov 12, 2020):

What are the exact commands you're running to start it? Can you post your config file and some log output as well.

<!-- gh-comment-id:725757777 --> @pirate commented on GitHub (Nov 12, 2020): What are the exact commands you're running to start it? Can you post your config file and some log output as well.
Author
Owner

@jmcree commented on GitHub (Nov 12, 2020):

Hey. You can close this.. I was just going though and getting all of the screenshots and logs for you and had an idea.. instead of putting "server 0.0.0.0:8000" in the docker settings I manually start the server from the console "archivebox server 0.0.0.0:8000". well, in my attempts to move it to port 5000, i was putting 5000 here too. I just started it from using the 8000 (what i now realize the internal port, not my bridge port) and it pulls right up.

Now if I can only figure out how to use tags or categorize the different sites.

<!-- gh-comment-id:725770849 --> @jmcree commented on GitHub (Nov 12, 2020): Hey. You can close this.. I was just going though and getting all of the screenshots and logs for you and had an idea.. instead of putting "server 0.0.0.0:8000" in the docker settings I manually start the server from the console "archivebox server 0.0.0.0:8000". well, in my attempts to move it to port 5000, i was putting 5000 here too. I just started it from using the 8000 (what i now realize the internal port, not my bridge port) and it pulls right up. Now if I can only figure out how to use tags or categorize the different sites.
Author
Owner

@cdvv7788 commented on GitHub (Nov 12, 2020):

Tags can be added from the admin in the latest version. You can build the image yourself with the contents of master
while we release a new image.

<!-- gh-comment-id:725775261 --> @cdvv7788 commented on GitHub (Nov 12, 2020): Tags can be added from the admin in the latest version. You can build the image yourself with the contents of `master` while we release a new image.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#1849
No description provided.