xorinzor

It's shown as up, but not what service is running (checked using nmap) https://suip.biz/?act=nmap

I've learned over time never to trust output of applications themselves, but just to get it from the source. It can't hurt to check netstat just in case

Interesting, though you can kinda confirm it by checking the output of netstat -atunl | grep 51820

That has been tested already, it's closed. We're just trying to figure out why at this point. Could be completely unrelated to the port forwarding if there's no service listening to the port.

I've had no issues with my intel xeon upon rebooting. Wasn't aware of any issues with intel either. Did you notice my edit? If you checked the port I don't think that's the issue, but it can't hurt to make sure. Let us know what the logging tells you (do another port check to trigger it, as well as try to connect with a wireguard client)

Do you have a static IP configured for your unraid server? Are other ports on your unraid server reachable? What if you enable the logging in your router for that port, does that give you any indications? I use unraid 6.8.2 too, but it works fine for me. EDIT: the blurred local endpoint, just to make sure, isn't set to Unraids local IP, but your external IP. Correct? In which case, did your external IP perhaps change?

Did you confirm the Wireguard service to be running? I've had a few instances where it stopped itself after editing the config. Also, If you check the port using an online tool, is it open? if not, either the port is closed, not forwarded correctly, or nothing is listening on the port (ie: wireguard service disabled).

I've had this on the android app of wireguard happen too, it looks as if it's connected even when it isn't. Maybe your external IP changed? or your server got a different IP address invalidating the port-forwarding? Either way, if your unraid server doesn't show the device as connected, it isn't.

If you just put your USB-stick with the unraid installation in your computer, and access the config file at /boot/config/wg0.cfg you can remove the network from peer allowed IPs again, to see if that fixes it. Not sure why it'd cause your admin panel to become unreachable however, but either way, this way you can still access all config files from unraid. As well as some log files.

Ah, I wasn't aware that it sent the "start" request via the GUI as well. I assumed this was handled by the plugin on the backend. Not sure how the plugin handles these requests, but perhaps it'd be able to send the current state along with any request made, and restore the state to it's original state if needed.

I understand that the networks and containers get new ID's, that's why they're configured using the name of the network (ie: alias) rather then ID. If this however would be the reason of the problem, not just this single container should fail to start every time, but 7 others too. Since I have quite a few containers utilizing these networks, including 2 other containers using the "vpn" network, and starting at boot just fine.

the name "vpn" is just an alias that it resolves within the run command to the ID of the network. If the network were to change after the earlier 2 containers initialized I would run into the problem of those 2 not having a network connection, but they run completely fine. Took me a while to learn these things about docker too, no worries it's why I enjoy working with Unraid so much

I'm running into the issue where; after I edit a peer config (or add a peer) and hit the save/apply button, the wireguard service just stops. This happened both times when I was doing this remotely while connecting via Wireguard to my server. Obviously I'd understand if the service would need to restart to apply the changes, but it never comes back up. I have to manually start it again when I'm back home. When I make changes however, while I'm not connected to Wireguard, the service seems to stay up and running. Is this a known issue?

Unfortunately not I checked the entire syslog file, but this is the only line that stands out (anything from before the reboot has wiped itself since it's loaded in RAM). Apparently the error in the log file is different then the error the WebGUI gives. The WebGUI always says "no such container", but the log file seems to say the network doesn't exist. Jan 27 16:58:13 STORAGE rc.docker: medusa: Error response from daemon: network a2603ce63d6661af7f33861e9092ad3ac52d3ed21bf5774e1632c0f00caa3275 not found Jan 27 16:58:13 STORAGE rc.docker: Error: failed to start containers: medusa Which seems odd to me, because this same "--net='vpn'" parameter is used in the 2 docker containers before it, without error. If medusa required an internet connection, the error message should be different I assume? At least we're 1 step further haha. EDIT: these are my networks. NETWORK ID NAME DRIVER SCOPE 2679778bf026 br0 macvlan local c13b7c638210 bridge bridge local 5f6a3251a135 efkstack bridge local ded1db5fe48f host host local 9600105bc546 none null local 187af992fc33 vpn bridge local 7e1e3d9bd667 webhost bridge local

I am aware of that

There is no container defined as 'vpn', it's a separate docker network that I created, in which I configured a docker container as the gateway. This way, I don't require any order in which to start the containers. Either way, the "gateway container" is ordered to start first, with 2 other containers starting after it, after which the medusa container is launched. So I don't think this is the cause of the problem. I have multiple docker networks configured, none of my other containers show this issue.

That sounds like the same kind of setup I have. I also have 2 other docker containers on the same vpn docker-network which start before medusa, and those always start just fine. This is the run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='medusa' --net='vpn' --ip='10.10.0.5' --cpuset-cpus='0,1,4,5' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user0/Media/Series/':'/tv':'rw' -v '/mnt/cache/Downloads/':'/downloads':'rw' -v '/mnt/disks/system_ssd/appdata/medusa':'/config':'rw' -h medusa --cap-add=NET_ADMIN 'linuxserver/medusa' ;/mnt/disks/system_ssd/docker_post_startup/medusa.sh

That's the thing I thought of at first too, but after deleting the container, and re-installing it, the configuration screen was reset completely to it's default values. No added ports, default docker network, default system paths, etc. So all that it gets from the appdata folder is the medusa app configuration, but that shouldn't have any impact on the container itself, as it's just a mounted folder.

I run roughly 11 different docker containers on my Unraid (now 6.8.2) installation. Since the beginning I've always had the same issue, that the Medusa container after a reboot doesn't start, and when attempting to start it manually I get the error "no such container". To fix this, I always just go to container -> edit, edit a field so the "apply" button becomes available, and then click it. After this, the container works perfectly fine again. I also tried deleting the container and re-installing it, but the same issue keeps happening. Would appreciate some help in diagnosing this problem.

All PHP commands from this container are suddenly giving "Bus Error". This started yesterday. It's currently sending me an error mail roughly every 30 minutes because of the cronjob trying to execute `/usr/lib/php/sessionclean`. If I open the container console and run "php" or even just "php -v" I also get "Bus Error". EDIT: Having rebooted the entire Unraid server seems to have fixed it. Not sure what was going on, rebuilding the container didn't fix it. No disks are out of space, no other containers had issues.

I've been using unraid because a regular NAS wasn't cutting it for me anymore. Especially the fact that I can add docker containers makes it an OS that I absolutely love. I'll be building a 2nd machine which will run my gaming VM as well using Unraid, and it's also going to run heavier containers such as plex. Features I'd like to see added, though might be outside the scope of Unraid. Are features that can be found in for example proxmox. Having the ability to build a virtual network with switches, etc. would be really great to have. Docker already has this, but I feel like the VM section is pretty limited when it comes to it's features. (Though honestly I haven't really checked it thoroughly yet either, so maybe it already is possible albeit in a hack-ish way). Another feature that I still cant emphasize enough is 2-Factor authentication. Since we now have form-based authentication, this must be a feature that can be added without too much difficulty, yet dramatically improve security.

I used to run on 6.7.0, upgraded to the 6.8.0 RC6 build today, and am experiencing this problem now too. Same thing, only have 1 VM, when started they disappear (virsh list shows it running). When I create another VM, it re-appears in the list as "running".

This used to happen to me until I updated to 67.0 or so, now it just shows an empty window until all docker containers have updated, before outputting all the text at once. Haven't tried updating to 6.8.0 yet, but since I recognized this issue, I figured I might as well add my 2 cents.

sorry for the confusion. The last entry in the FAQ did indeed answer my question, thanks.