Bug: Frontend does not work

[JmzTaylor]

Is this urgent?

No

What parts are affected

Frontend

What are the Server/Client versions of KitchenOwl

docker latest as of today

What's the problem 🤔

Copy/pasted the docker-compose and ran. Only changed the url and JWT token. I can access the webui but all I get is cannot connect reach server.

Share your logs

backend
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
[uWSGI] getting INI configuration from wsgi.ini
*** Starting uWSGI 2.0.20 (64bit) on [Wed Jul 20 17:36:41 2022] ***
compiled with version: 10.2.1 20210110 on 12 June 2022 14:49:03
os: Linux-5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022
nodename: 31aee3399e3c
machine: x86_64
clock source: unix
detected number of CPU cores: 8
current working directory: /usr/src/kitchenowl
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** 
your processes number limit is 62630
your memory page size is 4096 bytes
detected max file descriptor number: 40960
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uWSGI http bound on 0.0.0.0:80 fd 3
uwsgi socket 0 bound to TCP address 0.0.0.0:5000 fd 6
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** 
Python version: 3.10.5 (main, Jun  7 2022, 18:49:47) [GCC 10.2.1 20210110]
Python main interpreter initialized at 0x55e4cafcf1b0
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** 
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 145808 bytes (142 KB) for 1 cores
*** Operational MODE: single process ***
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x55e4cafcf1b0 pid: 24 (default app)
uWSGI running as root, you can use --uid/--gid/--chroot options
*** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** 
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 24)
spawned uWSGI worker 1 (pid: 40, cores: 1)
spawned uWSGI http 1 (pid: 41)
/usr/local/lib/python3.10/site-packages/apscheduler/util.py:436: PytzUsageWarning: The localize method is no longer necessary, as this time zone supports the fold attribute (PEP 495). For more details on migrating to a PEP 495-compliant implementation, see https://pytz-deprecation-shim.readthedocs.io/en/latest/migration.html
  return tzinfo.localize(dt)
[pid: 40|app: 0|req: 1/1] 172.22.0.1 () {72 vars in 1228 bytes} [Wed Jul 20 17:36:54 2022] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 100 bytes in 95 msecs (HTTP/1.1 200) 2 headers in 72 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 2/2] 172.22.0.1 () {72 vars in 1228 bytes} [Wed Jul 20 17:37:23 2022] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 100 bytes in 3 msecs (HTTP/1.1 200) 2 headers in 72 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 3/3] 172.22.0.1 () {72 vars in 1228 bytes} [Wed Jul 20 17:37:23 2022] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 100 bytes in 2 msecs (HTTP/1.1 200) 2 headers in 72 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 4/4] 172.22.0.1 () {72 vars in 1228 bytes} [Wed Jul 20 17:37:23 2022] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 100 bytes in 3 msecs (HTTP/1.1 200) 2 headers in 72 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 5/5] 172.22.0.1 () {72 vars in 1228 bytes} [Wed Jul 20 17:37:24 2022] GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V => generated 100 bytes in 2 msecs (HTTP/1.1 200) 2 headers in 72 bytes (1 switches on core 0)


frontend

2022/07/20 17:36:39 [notice] 1#1: using the "epoll" event method
2022/07/20 17:36:39 [notice] 1#1: nginx/1.22.0
2022/07/20 17:36:39 [notice] 1#1: built by gcc 11.2.1 20220219 (Alpine 11.2.1_git20220219) 
2022/07/20 17:36:39 [notice] 1#1: OS: Linux 5.15.46-Unraid
2022/07/20 17:36:39 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 40960:40960
2022/07/20 17:36:39 [notice] 1#1: start worker processes
2022/07/20 17:36:39 [notice] 1#1: start worker process 38
2022/07/20 17:36:39 [notice] 1#1: start worker process 39
2022/07/20 17:36:39 [notice] 1#1: start worker process 40
2022/07/20 17:36:39 [notice] 1#1: start worker process 41
2022/07/20 17:36:39 [notice] 1#1: start worker process 42
2022/07/20 17:36:39 [notice] 1#1: start worker process 43
2022/07/20 17:36:39 [notice] 1#1: start worker process 44
2022/07/20 17:36:39 [notice] 1#1: start worker process 45
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/entrypoint.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/default.conf.template to /etc/nginx/conf.d/default.conf
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
192.168.0.150 - - [20/Jul/2022:17:36:54 +0000] "GET /assets/.env HTTP/1.1" 200 53 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "-"
192.168.0.150 - - [20/Jul/2022:17:36:54 +0000] "GET /version.json?cachebuster=1658338613642 HTTP/1.1" 200 91 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "-"
172.22.0.1 - - [20/Jul/2022:17:36:54 +0000] "GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V HTTP/1.1" 200 100 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "172.69.69.31"
172.22.0.1 - - [20/Jul/2022:17:37:23 +0000] "GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V HTTP/1.1" 200 100 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "172.69.69.15"
172.22.0.1 - - [20/Jul/2022:17:37:23 +0000] "GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V HTTP/1.1" 200 100 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "172.69.69.15"
172.22.0.1 - - [20/Jul/2022:17:37:23 +0000] "GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V HTTP/1.1" 200 100 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "172.69.69.15"
172.22.0.1 - - [20/Jul/2022:17:37:24 +0000] "GET /api/health/8M4F88S8ooi4sMbLBfkkV7ctWwgibW6V HTTP/1.1" 200 100 "http://192.168.0.250:8249/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36" "172.69.69.15"

Share your configuration

docker-compose is identical to docs minus the url.

[TomBursch]

Have you taken the docker compose of the main branch or the docs? I just looked an the main branch one is not up to date. It mainly differs in that you have to set front-url on the backend too.

[JmzTaylor]

I used the one in the docs here

[TomBursch]

Okay good, did you include the correct protocol, i.e. https instead of http? It has to exactly match what you would enter into the browser's url bar.

[JmzTaylor]

Yeah all I get is the screenshot below. In the logs it seems to be talking to the backend, but just something is going wrong with it

.

[TomBursch]

I'll test it out tomorrow, but one person in the matrix group just set up yesterday. So I'm not really sure where the problem could be here. The logs don't seem to give any indication what could be wrong. In most cases other people had setup the wrong url in either front or backend.
I'll see tomorrow. Let me know if you found a fix. Have you tried the desktop/phone app?

[JmzTaylor]

Yeah after log on it goes into a spinning circle and doesn't progress

[TomBursch]

I cannot reproduce this, the current configuration definitely works if setup correctly.

Yeah after log on it goes into a spinning circle and doesn't progress

So are you saying you can enter your username + password and then are stuck?

Would you mind sharing any browser request errors. Right click in your browser -> inspect -> network or open the developer tools and than click on network. Are there any CORS related issues? You might need to click on the green refresh button a couple of times for them to show up.

[JmzTaylor]

Yup. So this one is on me. Sorry about wasting your time. I was using the local http://private_ip:port instead of the domain I set up since my docker GUI was pointing to local. It just never clicked on why that wouldn't work. Using domain with nginx works without issue.

[TomBursch]

Haha no worries, glad it finally works. I think I need to update the documentation a bit, you're not the only one who struggled with that part 😄

[JmzTaylor]

Also, unrelated, I saw that a previous issue or two was stemming from unraid community apps template for this. I did a pull request with the maintainer of that template to fix the ports issue and it was merged so that should be fixed in the unraid world now

[TomBursch]

Awesome, thanks for the contribution!