SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

OnlyOffice RabbitMQ User fails #1370

New Issue
Closed
opened 2025-11-20 05:09:00 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:09:00 -05:00
Owner
Copy Link

Originally created by @Mariuss811 on GitHub (Jun 27, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

OnlyOffice

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/onlyoffice.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

When creating the LXC and accessing the example server and opening a doc, the page won't load up and no document shows up.
But I found an error on systemctl status ds-docservice.service

[AMQP] Error: Handshake terminated by server: 403 (ACCESS-REFUSED) with message "ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN.

This error indicates an authentication problem when OnlyOffice tries to connect to RabbitMQ. The cause can be incorrect credentials, missing permissions, or the user not being flagged as a management user.
Possible Causes:

  1. Incorrect Credentials: The username or password for RabbitMQ access configured in OnlyOffice are incorrect.
  2. Missing Management Tag: The configured user does not have the necessary rights to log in to the Management Interface.
  3. Missing Permissions: The configured RabbitMQ user does not have the required permissions (configure, write, read) for the used VHost (default is "/").

I managed to solve the issue by:

  1. Checking if the user exists fpr RabbitMQ sudo rabbitmqctl list_users In my case the User wasn't known.
  2. Creating the User manually sudo rabbitmqctl add_user onlyoffice_rmq password
  3. Set up the permissions. sudo rabbitmqctl set_permissions -p / onlyoffice_rmq ".*" ".*" ".*"
  4. Set the user tag. sudo rabbitmqctl set_user_tags onlyoffice_rmq administrator

After these steps, i could open up a document via ds-example service and edit it

🔄 Steps to reproduce the issue.

Install the LXC
Try to access the example server and open a doc
Fails to load up

❌ Paste the full error output (if available).

`
systemctl status ds-docservice.service

[AMQP] Error: Handshake terminated by server: 403 (ACCESS-REFUSED) with message "ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN.`

🖼️ Additional context (optional).

No response

Originally created by @Mariuss811 on GitHub (Jun 27, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? OnlyOffice ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/onlyoffice.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. When creating the LXC and accessing the example server and opening a doc, the page won't load up and no document shows up. But I found an error on `systemctl status ds-docservice.service ` `[AMQP] Error: Handshake terminated by server: 403 (ACCESS-REFUSED) with message "ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN.` This error indicates an authentication problem when OnlyOffice tries to connect to RabbitMQ. The cause can be incorrect credentials, missing permissions, or the user not being flagged as a management user. Possible Causes: 1. Incorrect Credentials: The username or password for RabbitMQ access configured in OnlyOffice are incorrect. 2. Missing Management Tag: The configured user does not have the necessary rights to log in to the Management Interface. 3. Missing Permissions: The configured RabbitMQ user does not have the required permissions (configure, write, read) for the used VHost (default is "/"). I managed to solve the issue by: 1. Checking if the user exists fpr RabbitMQ `sudo rabbitmqctl list_users` In my case the User wasn't known. 2. Creating the User manually `sudo rabbitmqctl add_user onlyoffice_rmq password` 3. Set up the permissions. `sudo rabbitmqctl set_permissions -p / onlyoffice_rmq ".*" ".*" ".*"` 4. Set the user tag. `sudo rabbitmqctl set_user_tags onlyoffice_rmq administrator` After these steps, i could open up a document via `ds-example service` and edit it ### 🔄 Steps to reproduce the issue. Install the LXC Try to access the example server and open a doc Fails to load up ### ❌ Paste the full error output (if available). ` systemctl status ds-docservice.service [AMQP] Error: Handshake terminated by server: 403 (ACCESS-REFUSED) with message "ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN.` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:09:00 -05:00
saavagebueno commented 2025-11-20 05:09:01 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 28, 2025):

Not really sure why it gives the error. The relevant code bellow sets RMQ parameters correctly:

RMQ_USER=onlyoffice_rmq
RMQ_PASS=$(openssl rand -base64 18 | tr -dc 'a-zA-Z0-9' | cut -c1-13)

echo onlyoffice-documentserver onlyoffice/rabbitmq-host string localhost | debconf-set-selections
echo onlyoffice-documentserver onlyoffice/rabbitmq-user string $RMQ_USER | debconf-set-selections
echo onlyoffice-documentserver onlyoffice/rabbitmq-pwd password $RMQ_PASS | debconf-set-selections

i would be supprised if only difference would be creation of rmq user inside LXC

@tremor021 commented on GitHub (Jun 28, 2025): Not really sure why it gives the error. The relevant code bellow sets RMQ parameters correctly: ```bash RMQ_USER=onlyoffice_rmq RMQ_PASS=$(openssl rand -base64 18 | tr -dc 'a-zA-Z0-9' | cut -c1-13) echo onlyoffice-documentserver onlyoffice/rabbitmq-host string localhost | debconf-set-selections echo onlyoffice-documentserver onlyoffice/rabbitmq-user string $RMQ_USER | debconf-set-selections echo onlyoffice-documentserver onlyoffice/rabbitmq-pwd password $RMQ_PASS | debconf-set-selections ``` i would be supprised if only difference would be creation of rmq user inside LXC
saavagebueno commented 2025-11-20 05:09:01 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Jun 28, 2025):

I went ahead and checked:

root@onlyoffice:~# debconf-get-selections | grep "onlyoffice"
onlyoffice-documentserver       onlyoffice/cluster-mode boolean false
onlyoffice-documentserver       onlyoffice/db-host      string  localhost
onlyoffice-documentserver       onlyoffice/db-name      string  onlyoffice
onlyoffice-documentserver       onlyoffice/db-port      string
onlyoffice-documentserver       onlyoffice/db-pwd       password        3sKaGCgZ4DqRo
onlyoffice-documentserver       onlyoffice/db-type      string  postgres
onlyoffice-documentserver       onlyoffice/db-user      string  onlyoffice_user
onlyoffice-documentserver       onlyoffice/docservice-port      string  8000
onlyoffice-documentserver       onlyoffice/ds-port      string  80
onlyoffice-documentserver       onlyoffice/example-port string  3000
onlyoffice-documentserver       onlyoffice/jwt-enabled  boolean true
onlyoffice-documentserver       onlyoffice/jwt-header   string  Authorization
onlyoffice-documentserver       onlyoffice/jwt-secret   string  867cb82f189511bb2d3cdd060cb26552
onlyoffice-documentserver       onlyoffice/plugins-enabled      boolean true
onlyoffice-documentserver       onlyoffice/rabbitmq-host        string  localhost
onlyoffice-documentserver       onlyoffice/rabbitmq-proto       string  amqp
onlyoffice-documentserver       onlyoffice/rabbitmq-pwd password        KPYgLNJRzTB4E
onlyoffice-documentserver       onlyoffice/rabbitmq-user        string  onlyoffice_rmq
onlyoffice-documentserver       onlyoffice/remove-db    boolean false
onlyoffice-documentserver       onlyoffice/wopi-enabled boolean false

All parameters are set correctly. Its most likely a bug in the installer, since user onlyoffice_rmq never gets created for some reason

@tremor021 commented on GitHub (Jun 28, 2025): I went ahead and checked: ``` root@onlyoffice:~# debconf-get-selections | grep "onlyoffice" onlyoffice-documentserver onlyoffice/cluster-mode boolean false onlyoffice-documentserver onlyoffice/db-host string localhost onlyoffice-documentserver onlyoffice/db-name string onlyoffice onlyoffice-documentserver onlyoffice/db-port string onlyoffice-documentserver onlyoffice/db-pwd password 3sKaGCgZ4DqRo onlyoffice-documentserver onlyoffice/db-type string postgres onlyoffice-documentserver onlyoffice/db-user string onlyoffice_user onlyoffice-documentserver onlyoffice/docservice-port string 8000 onlyoffice-documentserver onlyoffice/ds-port string 80 onlyoffice-documentserver onlyoffice/example-port string 3000 onlyoffice-documentserver onlyoffice/jwt-enabled boolean true onlyoffice-documentserver onlyoffice/jwt-header string Authorization onlyoffice-documentserver onlyoffice/jwt-secret string 867cb82f189511bb2d3cdd060cb26552 onlyoffice-documentserver onlyoffice/plugins-enabled boolean true onlyoffice-documentserver onlyoffice/rabbitmq-host string localhost onlyoffice-documentserver onlyoffice/rabbitmq-proto string amqp onlyoffice-documentserver onlyoffice/rabbitmq-pwd password KPYgLNJRzTB4E onlyoffice-documentserver onlyoffice/rabbitmq-user string onlyoffice_rmq onlyoffice-documentserver onlyoffice/remove-db boolean false onlyoffice-documentserver onlyoffice/wopi-enabled boolean false ``` All parameters are set correctly. Its most likely a bug in the installer, since user onlyoffice_rmq never gets created for some reason
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1370
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?