Squid

Something happened on your flash drive. Delete /config/plugins/community.applications.plg and /config/plugins/community.applications Reboot and you'll be good to go after a reinstall

Only outdated due to licensing restrictions imposed by memtest themselves

IDK. Definitely would be a hack upon the system that you'd have to figure out via modifying system files. I'm not going to spend the time to sort that out.

While I'm sure there may be many esoteric uses for assigning public IPs within a private LAN, I've never once seen an enterprise environment anywhere (ie: the network experts) who didn't use 10.x, 192.x, 172.x

Is this correct? IPADDR[0]="100.27.27.245" NETMASK[0]="255.255.255.0" GATEWAY[0]="100.27.27.1" Highly unusual to give the server a static IP address that's actually a internet address (and registered to amazon aws) Also, DNS_SERVER1="82.209.169.7" Never heard of this DNS server before... Doesn't mean anything in and by itself though. Probably best to use 208.67.222.222 and 208.67.220.220

Thanks. Not a bug as you discovered, but I'll handle that circumstance in the context menu

What files exist on disk1 in the system folder? Main, folder icon far right lets you explore

localhost refers to the IP address of the container itself. Try setting the elasticsearch variable to be the IP address of the server (and also set the applicable port of the container). Assuming of course you have elasticsearch installed

This is probably unlikely.

PhAzE plugins haven't been a "thing" since 6.2.0, and were marked as being incompatible at that time. Whether they worked or not was a crap shoot at that point. You will honestly get zero support for using those plugins and really need to move over to a docker container

Read back a couple of posts

Changed Status to Closed

Changed Status to Retest Changed Priority to Other

Couple of comments. Any error in the docker run command (and after editing and apply with your changes) root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='GitLab-CE' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRaidB" -e HOST_CONTAINERNAME="GitLab-CE" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9080]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/tynor88/docker-templates/master/images/gitlab_small.png' -p '9080:9080/tcp' -p '9443:9443/tcp' -p '9022:22/tcp' -v '/mnt/cache/appdata/gitlab-ce/config':'/etc/gitlab':'rw' -v '/mnt/cache/appdata/gitlab-ce/data':'/var/opt/gitlab':'rw' -v '/mnt/cache/appdata/gitlab-ce/log':'/var/log/gitlab':'rw' --env GITLAB_OMNIBUS_CONFIG="external_url 'https://git.example.com';nginx['custom_gitlab_server_config'] = "location /-/plantuml/ { \n proxy_cache off; \n proxy_pass http://plantuml:8080/; \n}\n";prometheus_monitoring['enable']=false;" 'gitlab/gitlab-ce' sh: line 1: n}n;prometheus_monitoring['enable']=false;: command not found The command failed. Results in the container "disappearing". This is because for all intents and purposes it does NOT exist anymore because the installation (ie: the docker run command) failed The appropriate method to get the app back installed is via Apps - Previous Apps and then it would show up the template with the changes you had made so that you can edit them appropriately to fix the error. Doing a search in Apps for it would also give you the option to either Reinstall from Previous or Install -> Install sets the template back to defaults and depending upon what paths etc you had made would result in data loss Technically the appropriate method to add an envronment variable is via the Add Another Path / Port / Variable and enter in the appropriate entry there. The system will automatically escape everything accordingly. Adding variables via the Extra Parameters does work however

You don't see this:

@geromme Did you figure out your problem and hide the post or is that inadvertent?

Then you've done a symlink or something because the situation with emby is not actually possible.

I'd double check what the paths are in your library. If you're inadvertently telling plex to search /mnt for the library then it will pick up everything If you're actually telling it to only look in /mnt/user/.... then if it's scanning the parent (/mnt) for media then it's a Plex bug and needs to be reported in their own forums (IMO this is unlikely) IMO, the most secure system is to map only the shares you need Plex to have access to (eg: /movies1 to /mnt/user/movies1, /movies2 to /mnt/user/movies2 etc). What you're effectively doing is letting Plex have access to all of your banking information (which are stored in /mnt/user/Banking), those "private" pictures of your wife stored in xXx etc. Up to you, but if Plex doesn't require access to the stuff you actually don't want it to have access to, don't give it access

I recall some people had issues with samba on 6.10

Reboot Then try again. Don't close the popup and then copy and paste the output of it. (I can't replicate so need to see who's not doing their job: the OS or CA)

Now that we are on the cusp of 6.11 stable being released, this plugin will probably get marked as being incompatible with OS versions 6.10.0+ The truth of the matter is that on 6.10 the dependencies don't exist, and need to be installed. The current method chosen (have the user manually install the dependencies) would be more or less akin to Unassigned Devices (or even worse UD+) not including the extra packages they require and asking the user to install them manually themself. If a plugin requires something not included in the OS, then it really should install it and not force the user to do package management themself.

Try the upgrade to 6.11

Seeing as how the last update to gfjardim/cups was 6 years ago, and I'm not particularly surprised Better off using this

The container is continually restarting (due to the --restart=unlessstopped) you need to go through it's logs / setup and figure out why it's doing that

What What version of the OS?