Issues with static site after moving to new server

Help
1

1. Docker Container abiosoft/caddy:php 1.0.3

2. How I run Caddy:

I moved my Webserver to a new Server. Most of my services are running well but static site is making issues. It is not displayed at all.

a. System environment:

Ubuntu server 18.0.4

b. Command:

paste command here

c. Service/unit/compose file:

docker run -d\
    --name caddy \
    --restart=always \
    -v /docker/config/caddy/Caddyfile:/etc/Caddyfile \
    -v /docker/config/caddy/log:/etc/log \
    -v /docker/config/caddy/.caddy:/root/.caddy \
    -v /media/daten/WEBSERVICEDATEN/caddy/www/:/srv \
    -p 80:80 \
    -p 443:443 \
    -p 2015:2015 \
    -e ACME_AGREE=true \
    abiosoft/caddy:php

d. My complete Caddyfile:

#######################################
#FOLDERS

mywan.my-wan.de {
  root /srv
  tls 1234@yahoo.de
  #tls off
  log    /etc/log/gcbilder-access.log
  errors /etc/log/gcbilder-errors.log
  gzip
}

############################################
#COPS AUF FILESERVER

ebooks.myurl.de {
  proxy / 192.168.100.11:8030
  tls 1234@yahoo.de
  basicauth / XXXX XXXX
  basicauth / XXXX XXXX
  log    /etc/log/ebooks-access.log
  errors /etc/log/ebooks-errors.log
  gzip

}

############################################
#NEXTCLOUD AUF FILESERVER

nc.myurl.de, nextcloud.mywan.my-wan.de, nextcloud.myurl.de, mywan2.my-wan.de, mywan2.myurl.de {
  proxy / 192.168.100.11:8020 {
    transparent
    websocket
  }
  tls 1234@yahoo.de
  gzip
   # client support (e.g. os x calendar / contacts)
  redir /.well-known/carddav /remote.php/carddav 301
  redir /.well-known/caldav /remote.php/caldav 301
  header / {
    Referrer-Policy "no-referrer"
    Strict-Transport-Security "max-age=31536000; includeSubdomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
  }
  log /etc/log/nextcloud-access.log
  errors /etc/log/nextcloud-errors.log
}

############################################
#bitwarden AUF FILESERVER

bw.myurl.de {
  proxy / 192.168.100.11:8040 {
    transparent
    insecure_skip_verify
  }
  proxy /notifications/hub 192.168.100.11:3012 {
  websocket
 }
 proxy /notifications/hub/negotiate 192.168.100.11:8040 {
  transparent
  }
  log    /etc/log/bw-access.log
  errors /etc/log/bw-errors.log
  gzip
  tls 1234@yahoo.de
}

############################################
#wordpress 

myurl.de {
  proxy / 192.168.100.11:8090 {
    transparent
  }
  header / {
    Referrer-Policy "no-referrer"
    Strict-Transport-Security "max-age=31536000; includeSubdomains"
    X-XSS-Protection "1; mode=block"
    X-Content-Type-Options "nosniff"
    X-Frame-Options "SAMEORIGIN"
    Referrer-Policy "same-origin"
  }
  log /etc/log/caddy.log
  errors /etc/log/caddy.errors
  tls 1234@yahoo.de
  gzip
}

############################################
#Syncthing AUF FILESERVER

sync.myurl.de {
  proxy / http://192.168.100.11:8384 {
    transparent
  }
  basicauth / homer yaq1XSW"
  log    /etc/log/sync-access.log
  errors /etc/log/sync-errors.log
  gzip
  tls 1234@yahoo.de
  timeouts {
  read none
  write none
  header none
}
}
############################################
#Guacamole Virtualbox

vm.myurl.de {
  proxy / http://192.168.100.11:8080/guacamole {
      transparent
      websocket
  }
  tls 1234@yahoo.de
}

3. The problem I’m having:

As described. On the old server Docker command is identically as on old server.
Folders are copies 1by1 and now i am facing this issue …

4. Error messages and/or full log output:

404 Site homer-s.my-wan.de is not served on this interface

logs: caddy.error:

21/Nov/2019:20:36:38 +0000 [ERROR 499 /favicon.ico] context canceled
21/Nov/2019:20:46:49 +0000 [ERROR 499 /favicon.ico] context canceled

nothing in gc-bilder-* logs

caddy container log

2019/11/21 21:11:17 http: TLS handshake error from 172.17.0.1:35558: no certificate available for 'mywan.my-wan.de'
2019/11/21 21:11:17 http: TLS handshake error from 172.17.0.1:35562: no certificate available for 'mywan.my-wan.de'
2019/11/21 21:11:17 http: TLS handshake error from 172.17.0.1:35566: no certificate available for 'mywan.my-wan.de'
2019/11/21 21:11:17 http: TLS handshake error from 172.17.0.1:35580: no certificate available for 'mywan.my-wan.de'
2019/11/21 21:11:23 [INFO] mywan.my-wan.de - No such site at :80 (Remote: 172.17.0.1, Referer: )

5. What I already tried:

I also tried with tls off to avoid tls in FOLDER section of my Caddyfile.
Without success

6. Links to relevant resources:

2

I don’t see this site in your Caddyfile.

This is concerning. I can see mywan.my-wan.de in the Caddyfile you’ve posted.

I would check to ensure that the Caddyfile you have posted is the same as the one that’s being loaded when you start Caddy and that there are no issues at startup with that Caddyfile.

3

Sorry for that …

Again a wired thing I am using caddy which is a couple of years now. It did not work no matter what I did or tried. Two days later … working like a charm … ???

Thanks anyway, next time my request for help will be more precise

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.