Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App quit when use https in DDNS #6

Closed
Aspire1Inspire2 opened this issue Nov 11, 2019 · 6 comments
Closed

App quit when use https in DDNS #6

Aspire1Inspire2 opened this issue Nov 11, 2019 · 6 comments
Labels
bug Something isn't working

Comments

@Aspire1Inspire2
Copy link

I have setup reverse proxy to use motioneye behind Apache2's https.
When I am trying to add the "https://my.web.address/motioneye/" string to the DDNS address field, the app will error out and quit.

@developerfromjokela
Copy link
Owner

Hello,

I tried myself entering that, and it crashes.
I'll try my best to fix that as soon as possible.

@developerfromjokela developerfromjokela added the bug Something isn't working label Nov 11, 2019
@developerfromjokela
Copy link
Owner

Small update: Got it working. There's little work left to do, then I'll publish the new update. 😉

@Aspire1Inspire2
Copy link
Author

Thank you! 😁

@3bT8b1stYeA2s
Copy link

Not sure if this helps but it seems to be the colon character ":" that is causing the app to crash. I experienced this after adding a "device" then trying to modify it just as Aspire1Inspire2 mentioned adding 'the "https://my.web.address/motioneye/" string to the DDNS address field"
I tried adding just the colon and it crashes.

FWIW I'm using nginx as reverse proxy.

@developerfromjokela
Copy link
Owner

Ok, so now it's working. Open this issue again if it occurs again. 😄

developerfromjokela added a commit that referenced this issue Jan 6, 2020
* Fixed bug #4
* Fixed bug #9
* Fixed bug #6
* Fixed bug #5

Signed-off-by: Developer From Jokela <developerfromjokela@gmail.com>
developerfromjokela added a commit that referenced this issue Jan 6, 2020
* Fixed bug #4
* Fixed bug #9
* Fixed bug #6
* Fixed bug #5

Signed-off-by: Developer From Jokela <developerfromjokela@gmail.com>
developerfromjokela added a commit that referenced this issue Jan 6, 2020
* Fixed bug #4
* Fixed bug #9
* Fixed bug #6
* Fixed bug #5

Signed-off-by: Developer From Jokela <developerfromjokela@gmail.com>
developerfromjokela added a commit that referenced this issue Jan 6, 2020
* Fixed bug #4
* Fixed bug #9
* Fixed bug #6
* Fixed bug #5

Signed-off-by: Developer From Jokela <developerfromjokela@gmail.com>
@rezzalex
Copy link

rezzalex commented Jun 2, 2022

Hello @developerfromjokela, I just switched to Nginx and I have the error message "unauthorized" when trying to access from WAN, then, if I refresh the screen :

https://mydomainname:443/motioneye/picture/1/current?_=xxxxx&username=xxx&signature=xxxxxxxxxxxxxxx

In my motioneye android client config, I have the full "https://mydomainname /motioneye" url in DDNSHOSTAME and 443 in DDNS port.

Here is my NGINX.conf :

location /motioneye/
{
  rewrite ^/motioneye/?(.*) /$1 break;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_set_header X-Scheme $scheme;
  proxy_pass http://192.168.xx.xx:xxxx/; #local ipno to motioneye
  proxy_read_timeout  90;
}

location /video/ {
proxy_pass http://192.168.x.xx/video/;
proxy_read_timeout 86400;
}

location /image/ {
proxy_pass https://192.168.xx.xx/image/;
proxy_read_timeout 86400;

}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants