mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Bad gateway #2031
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2031
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fabry891 on GitHub (Sep 7, 2021).
Hi, I've installed home assistant and motioneye as docker. Home assistant work very fine.
But if I try to open the motioneye web interface, It show "502: bad gateway". I try with different browser.
What is the cause?
This is motioneye log:
@starbasessd commented on GitHub (Sep 7, 2021):
Which docker run command are you using for motioneye?
motionEye docker uses the same port as motioneye, 8765 for the WebGUI.
For some reason it is mentioning 28765.
@fabry891 commented on GitHub (Sep 8, 2021):
Hi, thanks for your reply.
I don't know which docker run command I'm using for motioneye. I've installed it via home assistant - supervisor page.
Do you suggest install motioneye via docker run command?
@starbasessd commented on GitHub (Sep 8, 2021):
I recommend not using HA or Portainer to supervise motionEye in a docker container.
I have several systems running docker in Ubuntu Server, Debian Server RaspberryPiOS Lite, in VMs and RPi3B+s and RP4s, and all run well as their own docker. There are many tickets open (and closed) where there are issues with HA and Portainer in the motionEye Github and Google groups. When run with it's own docker run, connected to HA, it's easier for us to see any issues.
@starbasessd commented on GitHub (Sep 11, 2021):
What have you found running motionEye docker container by itself?