Just noticed that the docker process is listening on tcp6, and curl with curl -k 127.0.0.1:8443
failed like remote access. Maybe that’s the problem?
root@xxx:~# curl -I -k https://localhost:8443
HTTP/1.1 401 Unauthorized
X-Powered-By: solid-server
Vary: Accept, Authorization, Origin
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Authorization, User, Location, Link, Vary, Last-Modified, ETag, Accept-Patch, Accept-Post, Updates-Via, Allow, WAC-Allow, Content-Length, WWW-Authenticate
Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, DELETE
Link: <.acl>; rel="acl", <.meta>; rel="describedBy", <http://www.w3.org/ns/ldp#Container>; rel="type", <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"
WWW-Authenticate: Bearer realm="https://localhost:8443", scope="openid webid"
Content-Type: text/html; charset=utf-8
Content-Length: 931
ETag: W/"3a3-Vl2/OEszkJiyFXJbo/jVIeUC0"
Date: Thu, 29 Nov 2018 08:42:36 GMT
Connection: keep-alive
root@xxx:~# curl -I -k https://127.0.0.1:8443
HTTP/1.1 404 Not Found
X-Powered-By: solid-server
Vary: Accept, Authorization, Origin
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Authorization, User, Location, Link, Vary, Last-Modified, ETag, Accept-Patch, Accept-Post, Updates-Via, Allow, WAC-Allow, Content-Length, WWW-Authenticate
Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, DELETE
Content-Type: text/plain; charset=utf-8
Content-Length: 9
ETag: W/"9-0gXL1ngzMISxa6S1zx3F4wtLyg"
Date: Thu, 29 Nov 2018 08:42:44 GMT
Connection: keep-alive