It is on a specific service. Creating new one shows the logs (also using CLI).

How can I fix the service that shows no logs?

I narrow it down to a specific use case where the logs are not being shown.

When a volume is attached to the service I cannot see the logs.

Creating new service - seeing logs ->

disconnecting the volume from old service - starting to see logs ->

connecting the volume to the new service - From now on, I cannot see the logs

I am now creating a new volume and attaching it to the new service to see if that helps

Using a new volume attached to the service fix the issue.

Weird and annoying, I need to restore my filesystem...

This is a known issue - Railway has confirmed in similar reports that volumes can cause deploy logs to not appear, even when the service is running fine (it's a visual/UI bug on their end). Creating a fresh volume is the correct workaround. To restore your data, you could temporarily spin up a utility container with both volumes attached and copy files from the old one to the new one before detaching the broken volume.