T
Twenty4mo ago
Volkan

Problem with v1.4.1 I have an error

I update the version of v1.4.1 however I couldn't access to the CRM anymore. Can you help me?
No description
14 Replies
ɃØĦɆᵾS
ɃØĦɆᵾS4mo ago
Could you check for errors in logs or in devtools in browser?
Volkan
VolkanOP4mo ago
here it is
No description
ɃØĦɆᵾS
ɃØĦɆᵾS4mo ago
Could you check the version of your database located at core.workspace.version?
Prastoin
Prastoin4mo ago
Could you please share the response error Logs in twenty-server too 🙂
Volkan
VolkanOP4mo ago
Just wait a second I am showing I am using railway for deployment Where can i find this I don't know
ɃØĦɆᵾS
ɃØĦɆᵾS4mo ago
According to this manual, you have to find Observability tab https://docs.railway.com/guides/logs
Viewing Logs | Railway Docs
Viewing Logs | Railway Docs
Learn how to view and filter build, deployment, environment, and HTTP logs on Railway.
Volkan
VolkanOP4mo ago
I thing I found: 2025-08-26 11:43:00.082 UTC [366] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41. You were right @bob the problem is database version What should I do?
Prastoin
Prastoin4mo ago
@Volkan could you please share the whole logs trace ?
Volkan
VolkanOP4mo ago
Like that @prastoin
No description
Prastoin
Prastoin4mo ago
What twenty railways configuration are you using ?
PikaDot
PikaDot4mo ago
I have the exact same problem!
Volkan
VolkanOP4mo ago
do you want me to share the link?
Prastoin
Prastoin4mo ago
Not the same problem. PikaDot missed 1.3 upgrade https://discord.com/channels/1130383047699738754/1409869675499880538
charles
charles4mo ago
@Volkan could you share the network tab of your browsers (the errors you seen in the FE come from error on the queries sent to your BE). I'm interested in their response, one of them (likely /metadata will contain an error that will help troubleshoot)

Did you find this page helpful?