Bureaucromancer

Also getting the 404 on an apparently running instance and a quick update. For whatever reason I had it set to the dev branch. Reverting to master resolved it, though I almost wonder if it was the act of updating more than the branch that fixed it…

Will report back shortly, but in the usual line of my issues being caused by the bloody obvious, I think this just boils down to insufficient RAM.

So I've seen a couple of other fairly inconclusive threads on this, but my symptoms really are just that VMs on this host crash, sometimes in a few minutes, sometimes they last an hour or two. It seems to be happening regardless of host OS, and is happening with multiple VMs. The notable things I've seen are repeated entries in the libvert log: virNetSocketReadWire:1791 : End of file while reading data: Input/output error The last entries in the VM log are inevitably: qxl_send_events: spice-server bug: guest stopped, ignoring 2023-02-24 04:30:05.516+0000: shutting down, reason=crashed Diagnostics are attached from moments after the last instance of this, but I'm not really seeing much to go on here... Any suggestions? hda-diagnostics-20230223-2330.zip

Is there any hope of getting JGR's patch pack as an option / additional install for OTTD? I know there is actually already an AUR package for the JGR version specifically on Arch

Huh... something seems off. Things are definitely being stored in /appdata/transmission-home, but the container doesn't have a /config mapping at all.

This has started for me as well, although my uptime is more like a week; no idea what's up.

I'm getting "Connection Refused" with Bridge type.

Is there a working client config guide anywhere? Link is to the forum home page.... Edit: https://web.archive.org/web/20160807091818/http://lime-technology.com/forum/index.php?topic=19439.0 Very old, but it does still work if you have an idea what you're looking at. Short version is that the one click install works, and ovpn files go in an openvpn directory you will need to create in the root of the flash drive.

Is there any way to change the VNC timeouts for either this docker or unraid as a whole? I've never had problems with VMs, but it would be immensely useful if I could at least not time out my session on Krusder (ideally I'd like to just resume it)...

Ok, I'm lost again. Had my reverse proxy (no external access) working for custom server names, but suddenly I'm getting connection refused errors from everything that should go through NGINX... I reinstalled the NGINX docker completly, and the test page works as expected, but my config file is either ignoring the port I'm redirecting to (or more likely as I see nothing in logs) not working at all. I've cut my default file down to a single docker for the moment, but can anyone see why this server entry would get me connection refused having previously been working? The plex server is working properly on 192.168.0.201:32400, or on plex.hda.home:32400 (which for the moment is from a local hosts file, but that will be addressed once I get a new router) so SOMETHING seems to be up with NGINX, but I havne't changed anything... server { listen 80; server_name plex.hda.home; location / { proxy_pass http://192.168.0.201:32400/; } } PS: And of course it worked the moment I posted this, having done nothing differently... Resolved I guess, but I'll leave this for the moment lest anyone have ideas. It's a stupidly simple config I know, but none of this is exposed externally except through a VPN, and the custom DNS is, like I said, entirely hosts based for the moment (I had dnsmasq working on my router, but for the moment I'm having to connect through a non-optional ISP device with no such abilities, looking at solutions, but frankly hosts works for me).

Ok, bumping for fix... privoxy was off... not entirely clear on the relationship between OVPN and privoxy, or why one of my or the required config changed (although from my limited understanding of privoxy it was always there and probably got turned off) but its working now (including confirmed that my ip is filtered).

Still stumped here... Completely removed app, reinstalled and recreated settings manually. Still refuses all connections. Tried installing the bare transmission, it's working as expected... Something's different between transmission and this version that's broken something, but I'm really lost now. Argh. Tried deleting my docker image in desperation. No change. Further update: I was able to get into my web interface by turning off the vpn_enabled flag in the docker, so I guess we now know that I'm dealing with a vpn issue rather than a transmission one, but does anyone know what might be happening here? To be honest I'm not even sure how to verify if the docker is connecting to my VPN correctly without being able to access the Transmission Web GUI.

As of today any attempt to connect to my install that has been working for well over a year gets me a connection refused error... seems like more or less the same issue, but it doesn't seem to give me anything helpful here... Any ideas out there?