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

Harmony Core on non-standard port #379

Open
shiblydangdang opened this issue Nov 1, 2024 · 2 comments
Open

Harmony Core on non-standard port #379

shiblydangdang opened this issue Nov 1, 2024 · 2 comments
Labels
question Further information is requested

Comments

@shiblydangdang
Copy link

Hi

We're trying to run HC on https on 8443 for example instead of 443. This all seems to work ok apart from when it tries to switch protocol to wss as this seems to default to 443. Any ideas how we change the default port for wss?

Thanks

@shiblydangdang shiblydangdang added the question Further information is requested label Nov 1, 2024
@SteveIves
Copy link
Contributor

Attached you will find a zip file containing example scripts that provide an example of how we generally start a Harmony Core service on Linux. You will see the HTTP and HTTPS port numbers in the file startserver.Production.config. The environment name (Production) is defined in the environment file. I included the appsettings filles so as to be a complete example, but much of the configuration settings in there is custom to a particular service that we maintain on behalf of a customer.

To start the service you use the startserver script with a parameter of either attach or detach.

Hope these help.

SampleConfigFiles.zip

@shiblydangdang
Copy link
Author

Sorry Steve, I thought I already replied to this!

We are using IIS so not sure if the above is relevant.

This is what happens when we have it on 443.......

443

As you can see there is one asp hub connection after GetToken then it does 101 switching protocols.

This is what happens on 8443......

8443

After the GetToken it tries to do 101 switching protocols but it times out and gets a 200 ok. It then creates a POST to asp hub for every request instead of using SignalR on WSS.

Any ideas?

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

No branches or pull requests

2 participants