Frontend stopped connecting to recorder.
See original GitHub issueI run owntracks recorder and frontend in swarm. After the latest recorder upgrade (version 0.8.8), the frontend stopped working properly. It is throwing:
10.0.1.11 - - [23/May/2022:07:56:26 +1000] "GET /?lat=-34.53xxx&lng=142.66xxx&zoom=6&start=2022-04-22T14%3A00%3A00&end=2022-05-23T13%3A59%3A59&layers=last,line HTTP/1.1" 200 471 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36"
10.0.1.11 - - [23/May/2022:07:56:26 +1000] "GET /config/config.js HTTP/1.1" 500 579 "https://owntracks.mydomain.com/?lat=-34.53xxx&lng=142.66xxx&zoom=6&start=2022-04-22T14%3A00%3A00&end=2022-05-23T13%3A59%3A59&layers=last,line" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36"
2022/05/23 07:56:26 [error] 9#9: *1 rewrite or internal redirection cycle while internally redirecting to "/config/config.js/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html", client: 10.0.1.11, server: , request: "GET /config/config.js HTTP/1.1", host: "owntracks.mydomain.com", referrer: "https://owntracks.mydomain.com/?lat=-34.53xxx&lng=142.66xxx&zoom=6&start=2022-04-22T14%3A00%3A00&end=2022-05-23T13%3A59%3A59&layers=last,line"
10.0.1.11 - - [23/May/2022:07:56:26 +1000] "GET /api/0/list HTTP/1.1" 502 559 "https://owntracks.mydomain.com/?lat=-34.53xxx&lng=142.66xxx&zoom=6&start=2022-04-22T14%3A00%3A00&end=2022-05-23T13%3A59%3A59&layers=last,line" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36"
I hope you can point me to the right direction in order to fix this issue…
My docker-compose.yml:
version: "3.8"
services:
otr-recorder:
image: owntracks/recorder
volumes:
- /mnt/docker/docker-volumes/owntracks:/store
environment:
- OTR_HOST=mosquitto.mydomain.com
- OTR_USER=<edited>
- OTR_PASS=<edited>
- PUID=1000
- PGID=1000
- TZ=Australia/Melbourne
networks:
owntracks:
aliases:
- otr-recorder
otr-frontend:
image: owntracks/frontend
environment:
- SERVER_HOST=otr-recorder
- SERVER_PORT=8083
- TZ=Australia/Melbourne
networks:
- proxy
- owntracks
deploy:
labels:
- "traefik.enable=true"
- "traefik.http.routers.owntracks.rule=Host(`owntracks.mydomain.com`)"
- "traefik.http.routers.owntracks.tls.certresolver=letsencrypt"
- "traefik.http.routers.owntracks.entrypoints=https"
- "traefik.http.routers.owntracks.tls=true"
- "traefik.http.routers.owntracks.middlewares=authelia@docker"
- "traefik.http.services.owntracks.loadbalancer.server.port=80"
networks:
owntracks:
internal: true
proxy:
external: true
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Panasonic Arbitrator 360 Operating Guide - Page 75 of 89
Check that the network is connected. Wait for a while, then play again. 20114. Streaming can not be started. via the Front-End, because....
Read more >Backend "Running", Not Recording, Can't Connect [Resolved]
Yes, I have tried restarting the backend many times. While I do have separate frontends, the mythtv frontend on the same machine as...
Read more >History and logbook no longer working - Frontend
Recorder The recorder could not start, please check the log. my config.yaml looks like this: (sorry, formatting/pasting code not doing what ...
Read more >History/recorder errors when they are disabled #12601 - GitHub
The problem I don't use history, logbook and recorder integration - in my YAML configuration they are disabled.
Read more >Troubleshooting - SimpleScreenRecorder - Maarten Baert's
The most common cause is a problem with your audio settings. Try recording without audio to see whether this is the case. If...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Oh, it is just easier for me to test different things.
ENTRYPOINT starts the container with parameters that cannot be overridden with CLI parameters. CMD allows to do so.
In other words, when you specify:
then you cannot start your container with different parameter/script for example:
The above example will start your container with
/usr/bin/my-script.shregardless what you specify as a starting parameter. In fact/usr/bin/different-script.shwill be interpreted as a parameter for your entrypoint.When you use
instead, you can override the starting point, so the above command will start your container with
/usr/bin/different-script.sh.When you specify both ENTRYPOINT and CMD, then whatever you put into the CMD becomes a parameter for your entrypoint. For example:
will be interpreted as:
and you can override parameters with:
which will be corresponding to:
I hope this makes sense.
In my Dockerfile it can easily be moved to ENTRYPOINT. No problems with that 😉
Thank you.
Closing this now, as it’s been answered in https://github.com/owntracks/recorder/issues/388