Rocket Chat - Upgrading to 6.x stable branch - Caddy Errors

Upgrade Help
1

What version are you coming from?

rocketchat-server --channel=5.x/stable

What version are you going to?

rocketchat-server --channel=6.x/stable

What deployment method did you use to deploy?

Snap, ran a backup on the old host that does not support AVX/2 , imported it to a new host that does. Switched to the 6.x/stable branch.

Did you follow a particular doc? Which one?

What issues are you running into upgrading?

It imported without issue/errors, and was able to switch the branch and refresh it without issue.

Receiving Caddy errors:

2023-11-02T18:18:05-04:00 rocketchat-server.rocketchat-caddy[8277]: {"level":"info","ts":1698963485.607207,"msg":"using provided configuration","config_file":"/var/snap/rocketchat-server/1583/Caddyfile","config_adapter":""}

2023-11-02T18:18:05-04:00 rocketchat-server.rocketchat-caddy[8277]: run: adapting config using caddyfile: /var/snap/rocketchat-server/1583/Caddyfile:2: unrecognized directive: proxy

Caddyfile:

mysite.net:8080
proxy / localhost:3000 {
transparent
}

I have also tried:

http://mysite:8080

reverse_proxy localhost:3000

With this one, I receive: Unknown directive: reverse_proxy

Additional details:

snap get rocketchat-server
Key                Value
backup-on-refresh  enable
caddy              enable
caddy-url          https://mysite.net
https              enable
ignore-errors      false
mongo-oplog-url    mongodb://localhost:27017/local
mongo-url          mongodb://localhost:27017/parties
port               3000
siteurl            https://mysite.net:8080

What am I doing wrong? I have had a Rocket Chat server for a number of years now, I am upgrading due to the version of MongoDB no longer being supported and unable to upgrade on the current host due to the lack of AVX support.

Thank you

2

That error should be fine. Is caddy not working with the errors?

3

The snap, if it finds a Caddyfile, tries to start with caddy v2 first, which can throw errors like that, and if it fails (indicating the Caddyfile is of v1’s), starts caddy v1 with the config.

4

Thank you @debdut.chakraborty for your replies! However, I have abandoned the Rocket Chat platform, it’s just too messy to keep running. This message I hope that the developers read, I have been using Rocket Chat since 2017. Your Snap deployment documentation is severely out of date, there is no mention of CaddyV2 config. I have since switched platforms and dumped Rocket Chat, migrated the users over, and most likely will not be back.