You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
change port number, as instructed: docker run -i -t -d -p 8083:80 --restart=always -e JWT_SECRET=my_jwt_secret onlyoffice/documentserver
install example as instructed: docker exec XXXX sudo supervisorctl start ds:example
open example editor and create new document, be faced with the UI loaded but an error message:
Additional information
The documentserver log file shows the issue: it is trying to make an internal request on port 8083 (public facing port), when it is internally using port 80:
As seen in #1819 you can get around this by using the public network IP of the machine instead of localhost, but this is not a solution, just a workaround, and it won't work when you have a firewall in place. The document server should not do requests to the outside for its internal needs.
Also the documentation should not point to something that does not work.
The text was updated successfully, but these errors were encountered:
This issue is unique.
Operating System of DocumentServer
Docker
Version information
latest (011630116202)
Expected Behavior
Starting docker container on a different port than 80, example should work.
Actual Behavior
Example editor does not work at all.
Reproduction Steps
docker run -i -t -d -p 8083:80 --restart=always -e JWT_SECRET=my_jwt_secret onlyoffice/documentserver
docker exec XXXX sudo supervisorctl start ds:example
Additional information
The documentserver log file shows the issue: it is trying to make an internal request on port 8083 (public facing port), when it is internally using port 80:
As seen in #1819 you can get around this by using the public network IP of the machine instead of localhost, but this is not a solution, just a workaround, and it won't work when you have a firewall in place. The document server should not do requests to the outside for its internal needs.
Also the documentation should not point to something that does not work.
The text was updated successfully, but these errors were encountered: