MCMaestro Posted February 15, 2019 Share Posted February 15, 2019 This is the error I get in my server log when trying to enter either the unraid terminal or a docker container console: Feb 15 18:10:53 Tower nginx: 2019/02/15 18:10:53 [error] 4718#4718: *2927 upstream prematurely closed connection while reading response header from upstream, client: 192.168.0.100, server: , request: "GET /dockerterminal/binhex-plex/ HTTP/1.1", upstream: "http://unix:/var/tmp/binhex-plex.sock:/", host: "192.168.0.200", referrer: "http://192.168.0.200/Docker" Any idea what could be causing this? Diagnostics attached. Quote Link to comment
m8ty Posted May 3, 2019 Share Posted May 3, 2019 May 3 11:30:46 shoebox nginx: 2019/05/03 11:30:46 [error] 7825#7825: *408019 upstream prematurely closed connection while reading response header from upstream, client: 192.168.88.116, server: , request: "GET /dockerterminal/ApacheGuacamole/ HTTP/1.1", upstream: "http://unix:/var/tmp/ApacheGuacamole.sock:/", host: "192.168.88.8", referrer: "http://192.168.88.8/Docker" Same issue. Getting a 502 Bad Gateway nginx error when I try to enter a docker terminal. Unraid version 6.6.7 It's a common issue I encounter, usually fixed with a reboot. It may even resolve itself, but I'm not sure as I've learned to ignore the problem and hope it fixes it self or I've had to reboot unraid for some other reason. Quote Link to comment
Glassed Silver Posted May 13, 2019 Share Posted May 13, 2019 On 5/3/2019 at 8:36 PM, m8ty said: May 3 11:30:46 shoebox nginx: 2019/05/03 11:30:46 [error] 7825#7825: *408019 upstream prematurely closed connection while reading response header from upstream, client: 192.168.88.116, server: , request: "GET /dockerterminal/ApacheGuacamole/ HTTP/1.1", upstream: "http://unix:/var/tmp/ApacheGuacamole.sock:/", host: "192.168.88.8", referrer: "http://192.168.88.8/Docker" Same issue. Getting a 502 Bad Gateway nginx error when I try to enter a docker terminal. Unraid version 6.6.7 It's a common issue I encounter, usually fixed with a reboot. It may even resolve itself, but I'm not sure as I've learned to ignore the problem and hope it fixes it self or I've had to reboot unraid for some other reason. How do you ignore something like this? Usually you need to do something rather important when going into the terminal don't you? Personally I'm trying to migrate my Plex lib to my new unRAID server and getting 502'd on my way to the terminal is pretty bad. I usually try to avoid my root share as much as possible, guess I have no choice today... A terminal session should ALWAYS "just work". Quote Link to comment
Delarius Posted May 13, 2019 Share Posted May 13, 2019 I'm not entirely familiar with this specific way of getting a docker terminal but if it's not working - you can always just do this directly via: docker exec -it <container> /bin/bash so an example might be something like: docker exec -it ApacheGuacamole /bin/bash At least you can get logged in to a docker in this manner - as to why the gui isn't letting you, not sure. Quote Link to comment
m8ty Posted May 14, 2019 Share Posted May 14, 2019 2 hours ago, Glassed Silver said: How do you ignore something like this? Usually you need to do something rather important when going into the terminal don't you? Personally I'm trying to migrate my Plex lib to my new unRAID server and getting 502'd on my way to the terminal is pretty bad. I usually try to avoid my root share as much as possible, guess I have no choice today... A terminal session should ALWAYS "just work". At that point I usually start a ssh session through an actual ssh client via bitvise on windows or terminal.app on macos. There's a new update for unraid available, version 6.7.0. I've updated and hopefully the issue has been addressed 🤞 @Delarius has the right idea with the `docker` command Quote Link to comment
Glassed Silver Posted May 14, 2019 Share Posted May 14, 2019 2 minutes ago, m8ty said: At that point I usually start a ssh session through an actual ssh client via bitvise on windows or terminal.app on macos. There's a new update for unraid available, version 6.7.0. I've updated and hopefully the issue has been addressed 🤞 @Delarius has the right idea with the `docker` command Well that's certainly an option, true, but it's still quite the inconvenience. As for the 6.7.0 update: that's what I'm running and I'm experiencing this problem regardless. So unless we have different things going on triggering the same symptom I think it's fair to say it's unfixed. Quote Link to comment
MCMaestro Posted May 14, 2019 Author Share Posted May 14, 2019 Hey, if I remember correctly, in the end it wasn't to do with unRaid, and I think Chrome was the issue. Might seem strange, but try a different browser. MC Quote Link to comment
controlol Posted July 31, 2019 Share Posted July 31, 2019 On 5/14/2019 at 11:48 AM, MCMaestro said: Hey, if I remember correctly, in the end it wasn't to do with unRaid, and I think Chrome was the issue. Might seem strange, but try a different browser. MC Could you maybe explain why this is the problem. (yes it got solved by using firefox!) I can use terminal and VMs perfectly outside the house and when I connect to the external IP. It really blows my mind... ~ Controlol Quote Link to comment
trurl Posted July 31, 2019 Share Posted July 31, 2019 Works fine for me with Chrome. Perhaps it is some Chrome addon or something else interfering. If you have an adblocker, whitelist your server. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.