Logs show nothing
I tried to redeploy, restarted. Still the same. It is the NestJS server and it works well before. Still don't know what cause it.
29 Replies
what browser are you using?
Firefox
Dokploy: Version: v0.12.0
OK I see the logs now. But I do nothing. I guess it has some huge delay?
If you open the logs page and open the browser developer tools.
Go to "Network".
You should have websocket connections.
Do they show, do you see failed websocket connections or anything of that kind?
I see only http, no ws
and this error
Why can't I see more than 1000 log lines?
This error can be ignored.
There should be websocket connections because that's how the logs get communicated.
Dokploy spawns a shell, executes the terminal command
docker container logs --tail ${tail} --follow ${containerId} and relays the output over the websocket.
So if you have no websocket connections at all in the network tab you won't see any logs.
If you do see logs on your screen, there has to be a websocket connection.
I thought it was because of performance reasons but i'm seeing that the logs get rendered on the fly while scrolling.
It seems like a bug.
Maybe the xterm package is the limiting factor here, i'm not sure.
It seems like the scrollback buffer can be set for xterm. Which is unset in Dokploy defaulting it to 1000I have found one more issue,
If i deploy any app using docker compose,
And run it till 2000+ log lines (as per my app code), then stop the container, and redeploy again after changing some codo line,
I can still see old logs,but if you are using any other builder like Heroku, nixpack etc and do as i said above,
No old log will be available because after stopping the container, Dokploy deletes the container, so we can see old logs.
You want to retain the old logs, you mean?
Yes
then please create a new thread, this is about the connection
This is a feature request.
Would require changing the way logs work.
it is still not related to my issue (bug), that the connection to show logs is not established
But you said you are getting logs eventually right?
My app has been running for 15+ days, I want logs from the beginning.
Currently I'm using SFTP to get log files.
Create a new thread and @ me
it just show once on one service (frontend) and never shows on backend Nestjs
Only the latest 1000 log lines. After redeployment, old logs are deleted.
Ok
I was replying to Sang Dang.
Please make a new thread 😉
So the application is running properly.
But your logs are not loading?
Or is there more going on that is incorrect.
I run my Nestjs applications on Dokploy too.
yes the app run ok, only log is empty, I tried to turn off every extension but look like it has no effect
Okay, one moment.
If you check like I check here.
You can not find a websocket connection?
(ignore that it's Nextjs. it's my frontend for my Nestjs app)
thank you, let me check that way
ok I can see it now
I still not sure which cause it. Thanks for the helps anyway.
It gets pretty complicated pretty quickly (sadly).
If you see a websocket connection and it connects, but you see no output. Something is acting weird.
There can be a myriad of reasons for stuff not showing correctly.
I agree. Logs are hard. Providing tool for general and each service/app has different taste of how to work with logs make it harder. 🫂
I can see my log pop up, still don't know why all the debug messages are not shown, but at least sth was up
I will keep an eye on this issue and let you know if I found out anything