Hey, I just tried to deploy the Chatwoot template (https://railway.com/deploy/chatwoot) and it seems to deploy fine on my end. Have you tried to redeploy the entire template again?
-# I am going to bed now, so responses will be delayed.

Hey @Neilor Mendes, do you still have any issues with deploying Chatwoot on Railway?

Hello @uxuz sorry pal, didn't have time to get to it today. Will try tomorrow morning and let you know.

@uxuz I've tested it but seems the issue is still there, if you want to check the project is 50eb82ca-085b-4066-b8a1-fb7d5d5e7af4 environment 50eb82ca-085b-4066-b8a1-fb7d5d5e7af4

Hey, I do not have access to your project. Feel free to attach screenshots / logs instead.

this is the docker image I'm using ghcr.io/railwayapp-templates/chatwoot:Community

Interesting, I have found two Chatwoot templates and both seem to deploy fine on my end as I have just tested (although, one of them doesn't use any volumes for some reason, so I decided to unpublish it as it doesn't persist any data). Do you mind deploying the Chatwoot template by "Brody's projects" (it should be the second option when you search for templates via Create > Template)?

This is the last one that I deployed, but sure, I can try again, give me a minute

Same errors @uxuz …

I am going to try and deploy the template again, the error message you have shown in the deploy logs shouldn't affect the deployment at all.

Do you also mind increasing the healthcheck timeout?

let me try

increased it to 600

I'm checking your deploy logs mine even reachs the message you received at 14:46:56…. Tha last the line I have is the one asking to contact the autor of reline…

This is indeed the case and I still don't know why I can't reproduce this behavior with the application completely freezing once it logs out the warning. Technically speaking, the warning is just saying that "fiddle" will no longer be shipped with Ruby 3.5 (the application is using Ruby 3.4) and it is advised to include it in the gemspec (I assume that this for dependencies, similar to package.json in node applications), followed by the message to contact the library author that uses "fiddle" to do so.

What I can tell you if it help is if I remove the healthcheck path, the app kind of can be deployed, but when I ssh to it, it is still running the bundle exec and it doesn't finish ever

This step just doesn't finish

After deploying multiple Chatwoot templates, I have managed to get one that also fails to deploy. This non deterministic behavior is definitely not intended.

I know this doesn't sound like the best solution, but could you perhaps delete your old Chatwoot instances, their respective databases and then deploy the template again?

sure… I can do it

I'm kind of trying to help you to search for the root cause and look below, it is hangging here:

I have an idea

Do you perhaps have IPv4 private networking enabled?

Yes you do.

There is a known issue with IPv4 private networking where some packets get dropped, and this causes the connection to hang indefinitely.

This would explain that command getting stuck.

so you saying just to disable the ipv4 private and try again?

where exactly I can disable it?

found it, never mind

worked like a charm @Brody and @uxuz thanks a lot

Now it worked properly… Thanks @Brody and @uxuz

!s

/thread link