Using sqlpage's certificate management for a subdomain

[audionuma]

Hello,
I'm trying to run a sqlpage project at home using a subdomain from a domain I manage (project.domain.tld).

I have a subdomain working from my registrar point of view (project.domain.tld points to my public adress) and connecting to the website with http://project.domain.tld as url returns the expected page.

I have tried to setup a secure connection using sqlpage's integrated certificate management (as described in https://github.com/sqlpage/SQLPage?tab=readme-ov-file#https) and so my sqlpage.json looks like :

{
  "database_url": "sqlite:///etc/sqlpage/sqlpage.db?mode=rwc",
  "https_domain": "project.domain.tld"
}

After restarting the docker container, I can no longer connect to the website, but something has happened because the server refuses to connect in http mode, forces to https, but refuses any connection. This is the result either I try from the outside with the project.domain.url or from the LAN with the IPv4 address of the server.

In case it is to take into account, domain.tld already has a working certificate managed by the registrar.

Any clue or idea welcome, is this idea simply possible with a subdomain ? Is there a verification step towards an email from the domain used ? Thanks.

(If needed, the project code can be found here : https://framagit.org/audionuma/ministock)

[lovasoa]

Hello! Can you please run SQLPage in debug mode and paste the debug logs here?
As well as the exact error returned by your browser when trying to connect?

[lovasoa]

Also, you mention using docker. Did you use docker's port option (-p) to forward the https port? -p 443:443

[audionuma]

Thank you for your answer.

TL;DR : Problem solved. The issue was actually the mapping of port 443 that I hadn't set into the docker launch parameters.

Following your suggestion of mapping the 443 port, it seems I found out where the culprit was, not in sqlpage but in my poor knowledge of the Docker intricacies.

1. When beginning dev, I edited a small bash script to launch the sqlpage container with appropriate parameters and use it to launch the container.
2. When moving this script to the production server (If I may call so the Raspberry Pi2B that runs the website), I just added a --restart always to the script and used this script to launch the container. The container would nicely restart at boot time when rebooting the server.
3. Following your suggestion, I added a -p 443:443 to the script, and then $ docker restart sqlpage that seemed to work but I eventually noticed that it actually restarted the container as it had been launched first time, and not reparsing the arguments from my script.
4. $ docker rm sqlpage allowed me to relaunch the container with appropriate configuration, and voilà, I can now visit my site in a secure connexion.

The current working script :

#! /bin/bash

docker run -itd --restart always --name sqlpage -p 80:8080 -p 443:443 --volume "$(pwd)/src:/var/www" --volume "$(pwd)/configuration:/etc/sqlpage" lovasoa/sqlpage