aptalca
-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by aptalca
-
-
5 hours ago, MowMdown said:
So far only Deluge loads correctly.
Sonarr however only loads a blank page with "Sonarr Ver" at the top left corner...
What confuses me is how am I supposed to know what all I need to include inside the block? Every docker container requires quite a bit of different code to get them to work.
location ^~ /sonarr { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; proxy_pass http://192.168.1.200:8989/sonarr; include /config/nginx/proxy.conf; }Can you access http://192.168.1.200:8989/sonarr directly? Does it work fine?
Most of the container guis work with this basic config. The only ones I tried that need custom settings are nextcloud, emby and plex
-
4 hours ago, Muff said:
Yes and I haven't configured any vlans
Are you trying to access it at 192.168.1.17:32400/web ?
-
On 9/12/2017 at 3:59 PM, MowMdown said:
Are there any resources I can read up on to figure out this application?
I definitely didn't learn this stuff in my CSC courses and it's a real pain in the rear...
Want me to build/compile a custom Linux kernel... done!
Build a custom android rom from source... done!
Reverse engineer an android bootloader...done
Reverse proxy a docker... help!!!!
You can also check out this guide: https://forums.lime-technology.com/topic/54206-the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/
-
1
-
-
4 hours ago, Muff said:
Hi,
I'm in need of a little help with Plex and I hope that you can help me
I'm not sure why but for some reason I can't access my Plex server locally (via plex.tv works) and I get the following error:
Chrome on port 32400: ERR_EMPTY_RESPONSE
Chrome on port 32401: ERR_CONNECTION_REFUSED
Firefox on port 32400: Unable to connect
Firefox on port 32401: The connection was reset
The Plex Log:
------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... Atempting to upgrade to: 1.9.0.4252-d07c1f408 2017-09-14 09:40:06 URL:https://downloads.plex.tv/plex-media-server/1.9.0.4252-d07c1f408/plexmediaserver_1.9.0.4252-d07c1f408_amd64.deb [107649162/107649162] -> "/tmp/plexmediaserver_1.9.0.4252-d07c1f408_amd64.deb" [1] (Reading database ... 11381 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.9.0.4252-d07c1f408_amd64.deb ... Unpacking plexmediaserver (1.9.0.4252-d07c1f408) over (1.8.4.4249-3497d6779) ... Setting up plexmediaserver (1.9.0.4252-d07c1f408) ... ################################################################## # NOTE: Your system does not have udev installed. Without udev # # you won't be able to use DVBLogic's TVButler for DVR # # or for LiveTV # # # # Please install udev and reinstall Plex Media Server to # # to enable TV Butler support in Plex Media Server. # # # # To install udev run: sudo apt-get install udev # # # ################################################################## Processing triggers for systemd (229-4ubuntu19) ... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. Starting dbus-daemon [services.d] done. dbus[299]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.17. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.1.17 on br0.IPv4. Server startup complete. Host name is Muff.local. Local service cookie is 1670098298.
I've also setup apache docker so I can access my docker container via Internet.
Is this normal or should I be able to access my Plex server via the LAN address?
Thank you!
Are you on the same network subnet as the plex server? Are there vlans involved?
Post the container settings (screenshot) and which ip you're using to connect to it
-
5 hours ago, DanielCoffey said:
Doesn't Plex have some sort of metadata file with the thumbnails and tags that you picked for your movie collection? Where does that reside?
So far I have moved over the movies themselves and installed a fresh Plex docker onto the new NAS.
All the plex aplication data should be under the /config folder that you set in container settings
-
9 hours ago, DanielCoffey said:
I am in the process of setting up a duplicate of my unRAID NAS and would like to know how to move my Plex settings and metadata over from the old array to the new one.
Both machines are running unRAID 6.3.5. Both have the movies in exactly the same folder structure as I have already duplicated the media. Both are actually running the exact same Dockers (Plex and Krusader). Once I have migrated Plex over to the new array, the old one will have the Plex Docker stopped.
Is there a guide or FAQ that has this information?
Make sure you keep the mount points and the folder locations the same and it will be fine. I think I moved my plex install about 3 times over the last couple of years. No issues
-
8 minutes ago, WexfordStyle said:
Okay. But is using a reverse proxy with https and password protection actually a security risk!? I imagine it would be very secure as well, no?
Technically everything is a security risk. If a device is connected to others, there is always a security risk.
Openvpn happens to be much more secure than https and a password, because the password can be brute forced. Unless you use a firewall like fail2ban (works great when properly configured).
If a reverse proxied docker container gets hacked into, it would be like someone breaking into your car and stealing what's in the glove box. Not much. But getting the unraid gui hacked is like someone stealing your alarm code and getting into your home, where they can get all the valuables, and the car keys. That's why they recommend using a vpn for the unraid gui.
-
4 hours ago, sevenz said:
ErrorWarningSystemArrayLogin
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
-------------------------------------
_ _ _
| |___| (_) ___
| / __| | |/ _ \
| \__ \ | | (_) |
|_|___/ |_|\___/
|_|
Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------
User uid: 99
User gid: 100
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
2048 bit DH parameters present
SUBDOMAINS entered, processing
Sub-domains processed are: -d www.sevenz.ddns.net:23689
E-mail address entered: [email protected]
Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
An unexpected error occurred:
The request message was malformed :: Error creating new authz :: Invalid character in DNS name
Please see the logfiles in /var/log/letsencrypt for more details.
IMPORTANT NOTES:
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
/var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory
[cont-init.d] 50-config: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
and this
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
2048 bit DH parameters present
SUBDOMAINS entered, processing
Sub-domains processed are: -d www.sevenz.ddns.net
E-mail address entered: [email protected]
Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for sevenz.ddns.net
tls-sni-01 challenge for www.sevenz.ddns.net
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.sevenz.ddns.net (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for www.sevenz.ddns.net
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: www.sevenz.ddns.net
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for www.sevenz.ddns.net
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
/var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory
[cont-init.d] 50-config: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Here it is. I have no idea how to remove the port number from the nextcloud ddns (its forwarded via vpn).
There is no dns entry for the www subdomain. Either create it, or remove the subdomain setting from container settings.
I don't know what you mean by the port number with nextcloud ddns and the vpn
-
3 hours ago, MowMdown said:
Are there any resources I can read up on to figure out this application?
I definitely didn't learn this stuff in my CSC courses and it's a real pain in the rear...
Want me to build/compile a custom Linux kernel... done!
Build a custom android rom from source... done!
Reverse engineer an android bootloader...done
Reverse proxy a docker... help!!!!
There are mainly two methods to reverse proxy with nginx.
First one is the root url / base url / url prefix method. If your app already has a base url like sabnzbd by default does (you access it directly at http://ip:port/sabnzbd) or allows you to set one, then you use the location block in the nginx site config to proxy that app from the address https://yourdomain.url/sabnzbd
This is the easiest way to proxy. As long as you match the root url to the proxied location name, it should pretty much work with no effort.
If your app doesn't support the base url, where you can only access it at http://ip:port then you should probably use the second method, subdomain. That way, you would access it at https://appname.yourdomain.url this is done in a new server block in the nginx site config.
The default nginx site config that comes with this container has samples (commented out) for both.
There is also a ton of info in this thread and a couple of others in this forum.
-
7 hours ago, sevenz said:
Hello, I'm trying to install letsencrypt. I wonder what causes this certbot error --cert-path: no such file or directory.
Full log.
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing...
2048 bit DH parameters present
SUBDOMAINS entered, processing
Sub-domains processed are: -d www.example.com
E-mail address entered: [email protected]
Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
Generating new certificate
Sub-domains processed are: -d www.example.com
E-mail address entered: [email protected]
Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...
Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
cert.
certbot: error: argument --cert-path: No such file or directory
and here is the command after I press applied.
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="letsencrypt" --net="bridge" --privileged="true" -e TZ="Asia/Bangkok" -e HOST_OS="unRAID" -e "EMAIL"="[email protected]" -e "URL"="work..example.me" -e "SUBDOMAINS"="www" -e "ONLY_SUBDOMAINS"="false" -e "DHLEVEL"="2048" -e "PUID"="99" -e "PGID"="100" -p 8083:80/tcp -p 443:443/tcp -v "/mnt/user/appdata/letsencrypt":"/config":rw linuxserver/letsencrypt 5014fdf3443be36024babe333597136c12a6b95e2d19e52a32946480ffdeea1b
Any idea where I did wrong?
Is that the end of the log? I doubt it. That error is harmless. It means you just changed the settings so it is trying to revoke the previous cert before generating the new one. However, it seems last time there was an error an no cert was generated so it can't find it.
-
9 hours ago, thestraycat said:
Hi guys - A quick question about bulk book import...
I'm currently suffering from having my docker.img file totally fill up on large ebook imports...
I run a 50gb Docker ISO image... And when i point a large zip file of comics etc to Calibre it fills it up very quickly... Would i be right in assuming that /tmp for calibre needs to be mapped outside of the image? It seems cailbre ebook import grinds to a half when the docker image is totally full (not to mention it effects other running containers)
Havnt been able to confirm which temp folder calibre uses to do its mass imports but was assuming /tmp from within the container. I know calibre also has variables that can define this path https://manual.calibre-ebook.com/customize.html but not sure whether they are available to be used when running calibre as a container and whether they need to be built/passed through the unraid template to be used?
Any help would be awesome...
If calibre is indeed using the /tmp location (I don't know whether it does or not) you can simply map it to any location on your unraid in the container settings. No need to mess with calibre settings
-
2 hours ago, Roadini said:
Thanks for your help.
I restarted the server and saved the logs for docker and tower itself. I can see an error within the tower log. But it doesn't tell me anything. My docker is part of the cache drive (Image).
Wrong thread. You are using limetech's plex docker, not linuxserver.io's
And according to the logs, you are using a mounted share (/nas/music) which fails to mount when plex is attempted to be started
-
7 hours ago, FreeMan said:
Thanks, CHBMB! That's exactly what I'm looking for!
Now, if there was some way to ensure a minimum password length...
That was the second option I had proposed but chbmb gets all the credit. I see how it is ?
-
55 minutes ago, FreeMan said:
After rereading the first 5 pages about 20 times... I've got my LE/NGINX setup and running! (Thanks for the container and all the tips and tricks.
After reading the remainder of the 32 pages, my one remaining question is how do I get/give access to friends/family to actually be able to create/change their own NGINX passwords? I created mine by SSH into my unRAID box then running:
docker exec -it letsencrypt htpasswd -c /config/nginx/.htpasswd <username>
but I have people spread across the country, and they can't all do that themselves. To be fair, I could create accounts/passwords for them (which would likely be longer, ergo more secure), but I'd prefer to give them a way of doing it themselves.
Once I get this last piece in place, I can email out instructions & shut down all the other port forwards in the router and feel much better about my server.
Thanks again to the linux|server.io gang, especially @aptalca for putting this all together!
Glad to hear it's working for you. If you can give them vpn access, they can ssh or telnet into your unraid and run that command (without the -c option) and their username and password will be appended to the htpasswd file.
Or, you can have them create the one way encrypted hash and send that to you, which you can manually append to that file. That way, you won't know what their password is and it would be easy to set it up.
-
3 hours ago, vurt said:
Reading this, it looks like you can add a base url in ghost's config, and the config file I'm looking for is config.production.js which I found when I open up a terminal in the Ghost container:
I ran a "cat config.production.json" and see this:
{ "url": "http://localhost:2368/", "server": { "port": 2368, "host": "0.0.0.0" }, "database": { "client": "sqlite3", "connection": { "filename": "/var/lib/ghost/content/data/ghost.db" } }, "mail": { "transport": "Direct" }, "logging": { "transports": [ "file", "stdout" ] }, "process": "systemd", "paths": { "contentPath": "/var/lib/ghost/content" } }I'm assuming "url": "http://localhost:2368/" is what I need to change, to "url": "https://mydomain.net/vurtopia/".
But how do I edit the json file?
There's no /ghost in /appdata where all my containers are. I usually FTP into unRAID, find the folders and files I need, and edit them.
A bit lost in the CLI. There's no vi or text editor I can run.
It sounds like when you created that docker container, you didn't map the locations that hold your user data. You can use nano or vi to edit the file and restart the container. Don't recreate or update the container because you will lose all of your data since they are all inside the container.
-
5 hours ago, vurt said:
Hi everyone, wondering if someone can help me out with reverse proxy for Ghost (blogging) docker that I managed to install from Docker Hub.
I can access the blog locally at http://192.168.1.252:2368/.
I'm trying to reverse proxy it like I've done with all my dockers.
This is what I have, which semi-works:
#Config for Ghost location ^~ /vurtopia { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.252:2368/; }(I'm just repurposing the above from what I have for Couchpotato.)
I can get to the blog at mydomain.net/vurtopia but the page doesn't load fully, like its CSS is missing.
And if I tried to visit mydomain.net/vurtopia/ghost to access the admin page, it brings me back to the login page after I log in.
Can you add a root url to ghost? That's most likely your issue
-
21 hours ago, Roadini said:
Hello Guys,
have problems with autostart of plex docker. When I start the unraid server plex doesn't autostart even though the autostart button on dockers page is activated. I can start plex manually from within the dockers page. It works smooth when startet.
Can you guide me what to look for to fix my autostart problem? Which logs do you need to assist me with my autostart problem?
Post the docker log as well as a screenshot of your container settings.
Is the config folder on a mounted share/unassigned disk by any chance?
-
2 hours ago, upthetoon said:
Seeing the same issue on rc8q;
Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (~): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
Error: failed to start containers: letsencryptYour issue is that unraid gui is using port 443
See if you can turn off https in unraid settings. Then you should be fine
-
If the unraid rc truly requires port 443, then you would only need a new ip with port 443 open for the letsencrypt container, not the rest of the containers.If I want to continue using this container for reverse proxy, combined with the new RC with LetsEncrypt support, I'm going to need to use my second NIC and assign all my Docker containers their own IPs in order to not have a port 443 conflict, right? I'm having some trouble visualizing how best to move forward...
I believe the new unraid rc uses a limetech hosted ddns and gets the certs for the addresses on their server (everyone gets a randomized unique string added to limetech's address). The certs would not be for your own domain, but the custom domain limetech assigns you. Theoretically they should be able to let you use a different port for the connection between their server and yours, although I'm not sure if that's implemented. -
If you remove the subdomains field in the container settings, that change should persist through updates. If it doesn't, it's an unraid gui issue.Every time this updates itself, it fails to load as I don't have a www subdomain. The only way I can then get it to work is to edit the container and remove the subdomains section. Nothing in my setup changed so I'm assuming something in the way the docker works changed.
How can I get around this? -
That's harmless.Hi guys,
I keep seeing these errors during cert renewal even though the certs are renewed successfully.
cronjob running on Mon Sep 4 16:07:17 AEST 2017Running certbot renewSaving debug log to /var/log/letsencrypt/letsencrypt.log-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/www.XXX.com.conf-------------------------------------------------------------------------------Cert is due for renewal, auto-renewing...Running pre-hook command: s6-svc -d /var/run/s6/services/nginxHook command "s6-svc -d /var/run/s6/services/nginx" returned error code 111Error output from s6-svc:s6-svc: fatal: unable to control /var/run/s6/services/nginx: No such file or directory-------------------------------------------------------------------------------new certificate deployed without reload, fullchain is/etc/letsencrypt/live/www.XXX.com/fullchain.pem-------------------------------------------------------------------------------Congratulations, all renewals succeeded. The following certs have been renewed:
Has anyone encountered these before and what's the resolution please?
Cheers.
It's trying to reload nginx after cert renewal but failing, because nginx is not running yet, since the renewal script is running during container start. Nginx will be started later with the new certs loaded.
If the script was running via cron at 2am, nginx would have been running, and would have been reloaded properly.
Either way everything works fine.-
1
-
-
I didn't interpret his reply as sarcastic at all. I do have the same genuine questions. Is there a reason I should be worried about sharing the drive serial numbers? If so, (as jonathanm suggested) the anonymizer can be modified to redact those as well (it already redacts a bunch of personal info). None of us want to post personal identifiable info online in this day and age. If not, we understand it's your personal decision and it's cool.
I didn't make a request for them not to be. My business is my own as to why I'd rather they not be displayed. I would have taken you seriously if you weren't a smart ass about it in your rhetorical question. But so seems to be the trend here in these forums anymore. So many abrasive replies to those with questions, concerns, etc. A sense of entitlement almost. I really do miss how things were 7 years ago, but alas, those days are seemingly done.
Keep in mind, I've demonstrated no less respect in my reply than I was extended in yours.
-
Edit the container settings, open advanced view and you'll see the field for web ui. Plug the ip in thereThe link is going to the unraid IP, I would be surprised if unraid knows which IP goes to the container, since I think with macvlan there is no communication between the host and docker, but I could be wrong. I'm actually on 6.3.5, so not one of the RC's.
I'm thinking it is something with the docker template (maybe), since the only system change was getting the updated version of the docker. Here's a link about where it used to be, which is under docker config advanced settings, Either way, it's not a big issue, since the docker works fine, Just annoying when I try to use the built in link.
-
What are you trying to do? Can you access the admin interface? If so openvpn-as is running fineThe /admin/ at the end is just to access the admin setting. Just http://:943 has worked before but just brought up a different ui for simple connecting and downloading profiles.
If you're just trying to access the cert download page, the address without admin should redirect you to /connect or something like that where you can login as the user. I noticed a redirect issue before (related to client OS and browser) but it's an openvpn-as thing, not docker related.
(Support) Aptalca's docker templates
in Docker Containers
Posted
If the drives are mounted on the host, you can map those locations in the container settings