Skip to content
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

Error of socket when API is not on default port (8443) #411

Open
BZHunt opened this issue Dec 1, 2022 · 1 comment · May be fixed by #412
Open

Error of socket when API is not on default port (8443) #411

BZHunt opened this issue Dec 1, 2022 · 1 comment · May be fixed by #412

Comments

@BZHunt
Copy link

BZHunt commented Dec 1, 2022

Hello,

We have identitified an issue affecting our configuration in production.
As our pwndoc instance is configured on a non-standard port (8443), it seems that the websockets cannot correctly establish a connection to the backend as the associated configuration seems hardcoded (non-dynamic).

Therefore any change in the defined ports requires a full regenaration of the configuration files.

We are opening a PR to provide a dynamic configuration based on the windows.location.port :)

BZHunt added a commit to BZHunt/pwndoc that referenced this issue Dec 1, 2022
@BZHunt BZHunt linked a pull request Dec 1, 2022 that will close this issue
@Xitro01
Copy link

Xitro01 commented Feb 7, 2024

Same issue for me.
#505

Manually updating the pull request does not solve this issue for me, any ideas?
Probably need to edit this inside the docker container itself, but not sure at which location. And yes I know it will not be persistent if I repull the image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants