Most of my deploy logs are not available no matter deploy was successful or not.
Successful one: Netlify App
Failed one: Netlify App
In both cases, I can’t see any logs on my dashboard. This is not specific to this site/project.
Most of my deploy logs are not available no matter deploy was successful or not.
Successful one: Netlify App
Failed one: Netlify App
In both cases, I can’t see any logs on my dashboard. This is not specific to this site/project.
Hey there,
I’m not able to reproduce the error – is this still problematic for you?
Yes it is. What can I do to help to investigate this?
Hi, @amankkg, would you please check your browser developer tools for console errors? If you see any, please send us those errors?
Also, are you using a VPN when you access Netlify?
VPN on and off doesn’t matter. Chrome logs on Windows and Linux.
Reproduction:
[https://app.netlify.com/sites/amankme/deploys/5f15139a7c434700079df498
](Netlify App)Actual behavior:
GET [https://netlify-builds5.firebaseio.com/.lp?start=t&ser=27043544&cb=2&v=5
](https://netlify-builds5.firebaseio.com/.lp?start=t&ser=27043544&cb=2&v=5`) hangs in a pending state for some time1:05:49 PM: [ERROR] Deploy logs are currently unavailable. We are working on resolving the issue.
GET [https://netlify-builds5.firebaseio.com/.lp?start=t&ser=49628456&cb=1&v=5](https://netlify-builds5.firebaseio.com/.lp?start=t&ser=49628456&cb=1&v=5) net::ERR_CONNECTION_RESET
GET [https://netlify-builds5.firebaseio.com/.lp?start=t&ser=15863483&cb=2&v=5](https://netlify-builds5.firebaseio.com/.lp?start=t&ser=15863483&cb=2&v=5) net::ERR_CONNECTION_RESET
and also net::ERR_TIMED_OUT
one once per 3-5 errors. Source [https://app.netlify.com/vendors~firebase.bundle.js:331
](Netlify App)
PS: I tried to ping [netlify-builds5.firebaseio.com](http://netlify-builds5.firebaseio.com)
directly and it’s OK
Could you tell us if this happens with all plugins and extensions disabled? I agree it does not seem to be about OS or VPN, but those errors are not happening to anyone else, so I do not think they are necessarily caused by a config on our side - I suspect a configuration on your machine (such as a browser plugin) or local network (such as a misbehaving proxy) might be involved.
It didn’t depend on browser nor extension, already checked this. Maybe something on my internet provider level.
Apparently it seems to be working fine now however I did nothing…
Hi, @amankkg, thanks for letting us know it is resolved now. If you see this issue again, please let us know.