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

Could you please tell me how to change the port 443 in the OnlyOffice-doc connection? #2734

Closed
1 task done
yuanhuabiao opened this issue May 17, 2024 · 3 comments
Closed
1 task done

Comments

@yuanhuabiao
Copy link

This issue is unique.

  • I have used the search tool and did not find an issue describing my bug.

Operating System of DocumentServer

Docker

Version information

7.1

Expected Behavior

The issue with my OnlyOffice is that it fails to load, and upon investigation, it’s because it’s using the default port 443, whereas the public domain name uses port 843, causing the online documents to fail to load. How do I change the port from 443?

Actual Behavior

The issue with my OnlyOffice is that it fails to load, and upon investigation, it’s because it’s using the default port 443, whereas the public domain name uses port 843, causing the online documents to fail to load. How do I change the port from 443?

Reproduction Steps

No response

Additional information

image

@avdddd1111
Copy link

Hello @yuanhuabiao !

What kind of setup do you have? What did you change?

More details in the help center:
https://helpcenter.onlyoffice.com/installation/docs-community-install-docker.aspx

You can use an additional reverse proxy to set any external network port you need.
https://helpcenter.onlyoffice.com/installation/docs-community-proxy.aspx

@Rita-Bubnova Rita-Bubnova added the waiting feedback Issues that we waiting to be answered from author of issue label May 24, 2024
@yuanhuabiao
Copy link
Author

yuanhuabiao commented May 25, 2024 via email

@Rita-Bubnova Rita-Bubnova removed the waiting feedback Issues that we waiting to be answered from author of issue label May 27, 2024
@Rita-Bubnova
Copy link
Member

@yuanhuabiao, It's a good news.
I close this issue. Feel free to comment or reopen it if you got further questions.

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

No branches or pull requests

3 participants