Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing default ports not changing #545

Closed
2 tasks done
random1planet opened this issue Jun 8, 2024 · 1 comment
Closed
2 tasks done

Changing default ports not changing #545

random1planet opened this issue Jun 8, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@random1planet
Copy link

⚠️ Please verify that this bug has NOT been reported before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I am trying to add to instances of radarr, so I changed the port numbers so they didnt conflict. but it doesnt seem to do what it should and they are not accessible on the advertised port. I also had the same issue trying to install jellyfn and emby, which by default use the same ports.

👟 Reproduction steps

normal port config 7878:7878, changed to 7879:7879 in the compose file.

👀 Expected behavior

this should change the ui port to the new port

😓 Actual Behavior

cant access the url using the new port

Dockge Version

1.4.2

💻 Operating System and Arch

bookworm

🌐 Browser

edge

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

@random1planet random1planet added the bug Something isn't working label Jun 8, 2024
@cyril59310
Copy link
Contributor

Only the port before the colon needs to be changed (7879:7878). The port after the colon concerns the container and should not be changed.

7879 : 7878
host container

Repository owner locked and limited conversation to collaborators Jun 9, 2024
@louislam louislam converted this issue into discussion #546 Jun 9, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants