Grist - SSL error #6808
Replies: 3 comments 8 replies
-
|
@simplerethink im not sure why the template has port 443 , as according to image its 8484 so can you change the port on your url in coolify from 443 to 8484, save and redeploy ( not sure if you need to alter the SERVICE env to match) |
Beta Was this translation helpful? Give feedback.
-
|
@djsisson thanks for the response. I was just reviewing the image and saw I also tried adding But that didn't resolve the issue either. |
Beta Was this translation helpful? Give feedback.
-
|
@djsisson Right, I tried just the domain change and it did not resolve the issue, which is why I tried port binding. Yes, I did a redeploy with each change. I just deleted the entire project and started with a clean slate, changing only the url to I tried to get the proxy logs, but it's not showing anything. Clicking refresh button and stream log did nothing either. I'm using Coolify Cloud. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I set up a new project using the Grist service.
I set the Grist domain to https://grist.mydomain.com:443
When I deploy, the Grist service shows as
running(unhealthy)When I go to the domain in my browser, Cloudflare gives me an
invalid SSL certificateerror page, showing the issue is on the host.I don't have SSL issues with any other service, so I don't think the issue is with Cloudflare config.
Any idea what the issue might be?
Beta Was this translation helpful? Give feedback.
All reactions