Caddyを用いたnextcloudへのアクセスエラー

以下のサイトを参考にCaddyを用いてnextcloudをRaspberry piにインストールしました。

nextcloudへは192.168.10.aaaからhttp://192.168.10.xxx:yyyyyでアクセスし、初期画面までは出たものの、ユーザ情報やMariaDB情報を入力し、セットアップ完了を押下した後の応答がない状態です。
ホスト名（下記画像の箇所）の入力値をlocalhostから192.168.10.xxx:yyyyyなどに変更してリロードなどしていると通常のログイン画面になり、ログインすることができます。が、データのファイルが開けなかったり、初期で配置してあるファイルが開けなかったりととうまく通信が行えていないのが現状です。

上記の方法で無理やりログイン直後、デベロッパーツールでエラーを見ると以下のようになっています(ログイン直後のエラー項目は4つだが、他の画面へ遷移すると他のエラーも発生)。

GET http://192.168.10.xxx:yyyyy/ocs/v2.php/apps/notifications/api/v2/notifications 403 (Forbidden)
Shutting down notifications: [403] Forbidden
PROPFIND http://192.168.10.xxx:yyy/remote.php/webdav/ 403 (Forbidden)
Uncaught (in promise) TypeError: Cannot read property 'getElementsByTagNameNS' of null
    at Client._getSabreException (client.js?v=3b9f6278-0:421)
    at client.js?v=3b9f6278-0:485

また、各設定ファイルは以下のようになっています。

/etc/systemd/system/caddy.service

[Unit]
Description=Caddy HTTP/2 web server
Documentation=https://caddyserver.com/docs
After=network-online.target
Wants=network-online.target systemd-networkd-wait-online.service

[Service]
;Restart=on-abnormal
Restart=on-failure

; User and group the process will run as.
User=root
Group=root

; Letsencrypt-issued certificates will be written to this directory.
;Environment=CADDYPATH=/etc/ssl/caddy

; Always set "-root" to something safe in case it gets forgotten in the Caddyfile.
ExecStart=/usr/local/bin/caddy -log stdout -agree=true -conf=/etc/caddy/Caddyfile -root=/var/tmp
;-root=/var/tmp
;ExecReload=/bin/kill -USR1 $MAINPID

; Use graceful shutdown with a reasonable timeout
;KillMode=mixed
;KillSignal=SIGQUIT
;TimeoutStopSec=5s

; Limit the number of file descriptors; see `man systemd.exec` for more limit settings.
LimitNOFILE=8192
; Unmodified caddy is not expected to use more than that.
;LimitNPROC=512

; Use private /tmp and /var/tmp, which are discarded after caddy stops.
PrivateTmp=true
; Use a minimal /dev (May bring additional security if switched to 'true', but it may not work on Raspberry Pi's or other devices, so it has been disabled in this dist.)
;PrivateDevices=false
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
;ProtectHome=true
; Make /usr, /boot, /etc and possibly some more folders read-only.
;ProtectSystem=full
;   except /etc/ssl/caddy, because we want Letsencrypt-certificates there.

;   This merely retains r/w access rights, it does not add any new. Must still be writable on the host!
;ReadWriteDirectories=/etc/ssl/caddy

; The following additional security directives only work with systemd v229 or later.
; They further restrict privileges that can be gained by caddy. Uncomment if you like.
; Note that you may have to add capabilities required by any plugins in use.
;CapabilityBoundingSet=CAP_NET_BIND_SERVICE
;AmbientCapabilities=CAP_NET_BIND_SERVICE
;NoNewPrivileges=true

[Install]
WantedBy=multi-user.target

/etc/caddy/Caddyfile

192.168.10.xxx:yyyyy {

    root /var/www/html/nextcloud
    log /var/log/nextcloud_access.log
    errors /var/log/nextcloud_errors.log


    fastcgi / 127.0.0.1:9000 php {
            env PATH /bin
    }


    # checks for images
    rewrite {
        ext .svg .gif .png .html .ttf .woff .ico .jpg .jpeg
        r ^/index.php/(.+)$
        to /{1} /index.php?{1}
    }


    rewrite {
        r ^/index.php/.*$
        to /index.php?{query}
    }

    # client support (e.g. os x calendar / contacts)
    redir /.well-known/carddav /remote.php/carddav 301
    redir /.well-known/caldav /remote.php/caldav 301


    rewrite {
        r ^/remote.php/(webdav|caldav|carddav|dav)(/?)$
        to /remote.php/{1}
    }

    rewrite {
        r ^/remote.php/(webdav|caldav|carddav|dav)/(.+?)(/?)$
        to /remote.php/{1}/{2}
   }


    # .htacces / data / config / ... shouldn't be accessible from outside


        status 403 {
               /.htacces
               /data
               /config
               /db_structure
               /.xml
               /README
       }

    header / Strict-Transport-Security "max-age=31536000;"

}