MotionEye - Outside access with SSL

STUKguy · 19. Januar 2021

Morlan also so forgot to mention, Macom advised to use the subfolder as that what was used for the Nextcloud not sure if that will help?

Just looking through Macom instructions for setting up nextcloud and he has this section in there

Could this be what im missing?

STUKguy · 19. Januar 2021

Morlan Ive got to work kind of....for somereason my browser says its dangerous????? but i go to the webpage on my mobile phone using mobile data it says its secure, tried it on another mobile phone and it also came up as secure.

STUKguy · 19. Januar 2021

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 · 11. Februar 2021

Hey. Hoping you both can help.

Ever since i recelently updated swag i keep "502 Bad Gateway"and when i check the logs i get this

macom · 11. Februar 2021

Regarding update of the linuxserver/nextloud container there is a note on https://hub.docker.com/r/linuxserver/nextcloud

Zitat
If you are not customizing our default nginx configuration you will need to remove the file:
Code
/config/nginx/site-confs/default
Then restart the container to replace it with the latest one.

Maybe it applies to your case as well.

STUKguy · 12. Februar 2021

Thank you macom, just read through the post this might work, do you how I remove /config/nginx/site-confs/default? The post doesn't say where it is.

macom · 12. Februar 2021

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

STUKguy · 13. Februar 2021

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?

macom · 13. Februar 2021

Zitat von STUKguy

Should i remove this too?

If you did not do any modification to it, I would remove them also and restart the container.

STUKguy · 13. Februar 2021

Thank you macom , everything is working again

STUKguy · 14. Februar 2021

Hi macom , So this happend

is there away for me to reinstall nextcloud & swag with out having to delete it all and start again?

macom · 14. Februar 2021

Did you change anything?

STUKguy · 14. Februar 2021

macom other then the steps previously taken nope, i didnt even know the Ngix folders location till the ther day

macom · 14. Februar 2021

So yesterday it was working and today not? Something must have happened in between.

STUKguy · 14. Februar 2021

macom everything seems to be working again ??? i just restarted the whole machine and seems to have sorted the issue

Soma · 18. Februar 2021

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

# 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;

    }

}

Alles anzeigen

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

services:
  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

Alles anzeigen

Hope this helps anyone.

MotionEye - Outside access with SSL

STUKguy 20. Januar 2021

Jetzt mitmachen!

Tags