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

Bug in Dockge Agent #430

Closed
2 tasks done
EdgarM73 opened this issue Feb 17, 2024 · 0 comments
Closed
2 tasks done

Bug in Dockge Agent #430

EdgarM73 opened this issue Feb 17, 2024 · 0 comments
Labels

Comments

@EdgarM73
Copy link

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I have set up a second instance but couldnt use port 5001 for it.

When trying to connect the agent to this new instance with 5101 i received an error message "could not connect " or so.

Than i change to port 5001 and it worked from scratch.

👟 Reproduction steps

using port different to 5001

👀 Expected behavior

to be able to connect to agent

😓 Actual Behavior

not able to connect

Dockge Version

1.4.2

💻 Operating System and Arch

debian docker

🌐 Browser

chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

@EdgarM73 EdgarM73 added the bug Something isn't working label Feb 17, 2024
@louislam louislam added help and removed bug Something isn't working labels Feb 17, 2024
Repository owner locked and limited conversation to collaborators Feb 17, 2024
@louislam louislam converted this issue into discussion #432 Feb 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
None yet
Development

No branches or pull requests

2 participants