404s on all pages

[badmonky]

@nebulon, would love your advice on this.

[robi]

check your services UI and make sure you have the DBs running and if needed bump their memory.

[badmonky]

@robi my postgres is running and nowhere near the limits in services. Is there anything special for the cal.com app that I am missing? There were no instructions on the app page, so I expected it should just work once the app is installed.

[badmonky]

This post is deleted!

[robi]

@badmonky nope, try the demo server to compare..

[sparkwise]

We're seeing the same problem after updating to v1.2.1. All user pages are blank. @calcom/web:start: error connecting to engine: sql, type: postgres db: Error: connect ECONNREFUSED ::1:5432 Reverting to v1.2.0 now.

[girish]

@badmonky @sparkwise Can you give me more information about the setup? Fresh install or upgrading?

@badmonky it sounds like yours is a fresh install. So, you installed a fresh instance and everything is a 404?

[girish]

Fresh install atleast works just fine here on my test instance and also on the demo.

[girish]

There is something wrong. I left the app running for a while and I get non-stop:

Nov 21 11:42:37@calcom/web:start: error connecting to engine: sql, type: postgres db: Error: connect ECONNREFUSED ::1:5432

But the app itself curiously works!

[chetbaker]

I'm experiencing the same 404 problem here with an updated version

[girish]

OK, I have revoked com.cal.cloudronapp@1.2.1 . @chetbaker so 1.2.0 works, correct ?

[chetbaker]

@girish Yes, that's correct.

[3699n]

I am also experiencing the 404 problem with the latest version. While I can access the dashboard, all the booking links leads to 404s

[girish]

@3699n ah, that's very good information! I thought it was the dashboard that was 404ing

[chetbaker]

I'm sorry, that's exactly what happen: dashboard works perfectly, but the link to book is the one giving 404

[badmonky]

@girish yes, was a fresh install. I will try the rolled back version now.

[badmonky]

Confirmed, rolled back version seems to work

[girish]

The new version set NEXTAUTH_URL to kill some warnings. Looks like we have to live with the warnings.

[nebulon]

Does the 404 issue still persist with the latest app package?

[sparkwise]

Looks fine for us!