TeddyCloud frontend responds with 404

Hi.

i hope you could help me with my issue.

i followed the guide from Working docker-compose.yml file for creating the docker container
to add teddycloud to my docker-compose stack on my raspberry
it seems from log, that my toniebox is able to connect to teddycloud but i’m not able to access the frontend via browser/curl - only get 404

my docker-compose section

  teddycloud:
    container_name: teddycloud
    image: ghcr.io/toniebox-reverse-engineering/teddycloud:latest
    ports:
     - 80:80 
     - 443:443 
    mac_address: 66-66-66-00-00-01  # random 
    hostname: teddycloud
    dns:                                                   
      - "192.168.178.1"
      - "192.168.178.2" # pi-hole adress


    volumes:
      - ./teddycloud/certs:/teddycloud/certs
      - ./teddycloud/config:/teddycloud/config
      - ./teddycloud/data:/teddycloud/data
    restart: unless-stopped
    environment:
     - TZ=Europe/Berlin
    cap_add:
      - NET_ADMIN    
    networks:
      dockervlan:    
        ipv4_address: 192.168.178.101

curl:

curl -vvv --insecure https://prod.revvox                                           
*   Trying 192.168.178.101:443...
* Connected to prod.revvox (192.168.178.101) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):

* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Request CERT (13):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
*  subject: CN=TeddyCloud Server
*  start date: Jan 14 09:44:03 2004 GMT
*  expire date: Jan 14 09:44:03 2044 GMT
*  issuer: CN=TeddyCloud CA Root Certificate
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* using HTTP/1.x
> GET / HTTP/1.1
> Host: prod.revvox
> User-Agent: curl/8.4.0
> Accept: */*
> 
< HTTP/1.1 404 Not Found
< Connection: keep-alive
< Keep-Alive: timeout=300, max=1000
< Accept-Ranges: bytes
< Content-Type: text/html
< Content-Length: 156
< 
<!doctype html>
<html>
<head><title>Error 404</title></head>
<body>
<h2>Error 404</h2>
<p>The requested page could not be found</p>
</body>
</html>
* Connection #0 to host prod.revvox left intact

teddycloud log if trying from google chrome:

teddycloud  | INFO |server.c:0570:server_init| 0 open HTTPS connections
teddycloud  | WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
teddycloud  | WARN |tls_server_fsm.c:0260:tlsPerformServerHandshake| TLS handshake failure!
teddycloud  | INFO |server.c:0570:server_init| 1 open HTTPS connections

Many thanks

You must not change the volumes (data). This was you overlay the www dir with the webserver with an empty root directory.

Hi badbee,
thank you very much. i just downloaded the www folder from the github repo and now it works well.

No, don’t do that. You’ll get problems as soon teddyCloud is updated
Please fix your volumes.

yes, makes sense. Thank you very much again.