MotionEye - Outside access with SSL
-
- OMV 5.x
- gelöst
- STUKguy
-
-
-
Morlan and macom Thank you both, So i attempted what i wanted with Qbittorrent instead
Moved to nextcloud network
Edited "docker-compose.yml" subdomain to include qbitorrent
changed qbittorrent.subfolder.conf.sample to qbittorrent.subfolder.conf
Restarted Swag container
Then went to *******.duckdns.org/qbittorrent
Everything worked i could access it
Which got me thinking if the following would work
Edit qbittorrent.subfolder.conf.sample changed every mention of qbitorrent to motioneye and changed all 8080 port referances to 8765
Saved the file as motioneye.subfolder.conf
restarted Swag
went to *******.duckdns.org/motioneye
and haza!! everything worked, probaly should have wrote a guide on this im sure someone else will want the same thing everntually.
But thank you so much!!!
-
STUKguy
Hat das Label gelöst hinzugefügt. -
-
Regarding update of the linuxserver/nextloud container there is a note on https://hub.docker.com/r/linuxserver/nextcloud
ZitatMaybe it applies to your case as well.
-
-
In the config folder of your docker.
You can also search it with
find / -name site-confs
or install the locate plugin from omv-extras
-
macom Thank you again soo much,
I installed the plug in "locate" on omv-extra, then searched for "site-confs" which gave me 4 results. 2 in the SWAG folder and 2 in the nextcloud folder.
Used SSH to get to the location showen in the search result for SWAG typed in "rm -rf defaults" which deleted the folder then typed in "docker restart swag" went to my motion outside page and haza everything worked.
Even though everything is working again i get this error
**** The following nginx confs have different version dates than the defaults that are shipped. ****,
**** This may be due to user customization or an update to the defaults. ****,
**** To update them to the latest defaults shipped within the image, delete these files and restart the container. ****,
**** If they are user customized, check the date version at the top and compare to the upstream changelog via the link. ****,
/config/nginx/nginx.conf,
Should i remove this too?
-
Should i remove this too?
If you did not do any modification to it, I would remove them also and restart the container.
-
-
-
Did you change anything?
-
-
So yesterday it was working and today not? Something must have happened in between.
-
-
DISCLAIMER: This works if you already have other apps running on subdomain (nextcloud,plex,etc). and you have "SUBDOMAIN=wildcard" or "SUBDOMAIN=motioneye" added on you duckdns auth. (Maybe with other providers works also, I use duckdns)
If you have your setting working with subfolders, this is not the right file.
Thank you all for this. I have motioneye running since ever as a single stack but now is time to move it to SWAG,
After reading through, I've done a small "motioneye.subdomain.conf.sample" to add to SWAG "nginx/proxy-confs"
BIG Thank you to Morlan and macom for their tips:
Code
Alles anzeigen# Conf Sample to be used by SWAG Reverse Proxy for access via HTTPS to motioneye.yourdomain.url # Example: 'h**ps://motioneye.yoursubdomain.duckdns.org/' # For this to work properly, motioneye container must be included in the same stack as SWAG container (same docker-compose.yml) # That way, the containers are able to communicate with each other without any hassle. server { listen 443 ssl; listen [::]:443 ssl; server_name motioneye.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; # If you want access as "h**ps://motioneye.yourdomain.url/cams/ , change next line to "location /cams/" location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app motioneye; set $upstream_port 8765; # note: same port used on the docker-compose for motioneye set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # Add to comment this one since it already exists on "include /config/nginx/proxy.conf;" -->> proxy_read_timeout 120s; access_log off; } }
And the docker-compose.yml for motioneye that I previously had (just added it to the one with SWAG):
NOTE: This is for Raspberry Pi running arm32 OS
Code
Alles anzeigenservices: motioneye: image: ccrisan/motioneye:master-armhf container_name: motioneye volumes: - /etc/localtime:/etc/localtime:ro #Timezone Config / Do Not Change - /srv/dev-disk-by-label-DATA/appdata/motioneye:/etc/motioneye # Config Storage; This is my personal path; change accordingly - /srv/dev-disk-by-label-DATA/media/motioneye:/var/lib/motioneye #File Storage; This is my personal path; change accordingly devices: # Needed because I have a v4l2 nightvision cam on the RPi4 - /dev/video0 # Needed because I have a v4l2 nightvision cam on the RPi4 ports: - 8765:8765 # For error free, stick with this port # - 58001:58001 # Only needed for streaming; don't need it since I see real time on the webfront hostname: motioneye restart: unless-stopped
Hope this helps anyone.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!