Bug: web frontend working in browser but not in app

[Baton4986]

Is this urgent?

None

What parts are affected

Both

What are the Server/Client versions of KitchenOwl

Docker Image Version: v68 / Android App Version: 0.4.5

What's the problem 🤔

I can connect to the frontend via browser, but not via app (message: "Hmmmm. server can't be reached").

Share your logs

docker_front_1:
2023/06/28 16:45:10 [notice] 1#1: start worker process 36
127.0.0.1 - - [28/Jun/2023:16:45:40 +0000] "GET / HTTP/1.1" 200 1548 "-" "curl/7.88.1" "-"
127.0.0.1 - - [28/Jun/2023:16:46:10 +0000] "GET / HTTP/1.1" 200 1548 "-" "curl/7.88.1" "-"
127.0.0.1 - - [28/Jun/2023:16:46:40 +0000] "GET / HTTP/1.1" 200 1548 "-" "curl/7.88.1" "-"
127.0.0.1 - - [28/Jun/2023:16:47:10 +0000] "GET / HTTP/1.1" 200 1548 "-" "curl/7.88.1" "-"
127.0.0.1 - - [28/Jun/2023:16:47:40 +0000] "GET / HTTP/1.1" 200 1548 "-" "curl/7.88.1" "-"

Share your configuration

Apache Reverse Proxy Settings:
        ServerName my.kitchenowl.domain
        ProxyPass / http://127.0.0.1:8001/ retry=0
        ProxyPassReverse / http://127.0.0.1:8001/


docker-compose.yml:
version: "3"
services:
    front:
        image: tombursch/kitchenowl-web:latest
        ports:
        - "8001:80"
        depends_on:
        - back
        networks:
        - default
    back:
        image: tombursch/kitchenowl:latest
        restart: unless-stopped
        networks:
        - default
        environment:
        - JWT_SECRET_KEY=mysecretkey
        volumes:
        - kitchenowl_data:/data

volumes:
    kitchenowl_data:

networks:
    default:

[sailor-ITlab]

I probably have the same problem.
When I connect from the app via http everything works. But if I use https I get an error message in the app: "Hmmmm... the server was not reached".
Via the website everything works fine.
As a reverse proxy I use Nginx.

[TomBursch]

@ramon-kramer @sailor-ITlab Can you share logs of the frontend and backend when trying to connect with the app?

[Baton4986]

solved this! there was an issue with the ssl cert-chain, browsers didn't care for it but the app did.

[Baton4986]

@TomBursch THX by the way 👍

[sailor-ITlab]

The problem still exists for me.
I use a wildecard SSL certificate from Let's Encrypt.
So far it works everywhere and no browser has caused problems.
All traffic goes through a NGINX reverse proxy (Docker container: jc21/nginx-proxy-manager:latest).
Frontend Logs:
_kitchenowl-frontend_logs.txt
Backend Logs:
_kitchenowl-backend_logs.txt
Docker-Compose yml:
Docker-Compose-yml.txt

[TomBursch]

@sailor-ITlab sorry for the late response, are you still encountering this issue? I couldn't see any errors in your logs, could you share those that contain an error? Otherwise, I'll assume this is an issue with your reverse proxy setup and close this issue 🙂

[sailor-ITlab]

I also didn't see an error in the logs. But I think erveything is working with the reverse proxy too.
I can login via the webpage, but not the app.
When I use https the App shows, that there is no connection to the server. If I use http it shows the login screen

[sailor-ITlab]

@TomBursch I have solved the problem for me.
I have used an SSL certificate from Let's Encrypt so far. The app did not work with it.
Now I switched to a certificate from IONOS (they get it from: " GeoTrust - powered by DigiCert ") and everything seems to work.
Where the original problem is/was I unfortunately do not know.

[TomBursch]

Thanks for the update, I'm using Let's Encrypt everywhere too and have no issue with it. Maybe this was some android/iOS related issue or so. Will just close it and hope no one else has this issue.