You are giving it the -d flag. -d means “detached.” There are logs, you are just preventing yourself from seeing them.

Replace the -d with an -i (for interactive) and try again.

Have you completed the podman rootless setup in order to be able to use it? You may need to edit /etc/subuid and /etc/subgid to get containers to run:

https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md#etcsubuid-and-etcsubgid-configuration

More than likely, this might have something to do with podman being unprivileged, and this wanting to bind to port 80 in the container (a privileged port). You may need to specify a --userns flag to podman.

Running in interactive mode will give you the logs you want and will hopefully point you in the right direction.

Hi :)

If you’re already running an instance, you’re not going to have a good time of this on the same server unfortunately. The webserver config I ship assumes a single instance, and all of the handling assumes only one domain. You would have to basically modify my entire script to support something like this.

You can take a look at my advanced configuration page to figure out what files you can edit, but this would be a very manual process for what you want to do.

Apologies, but you would be better off deploying a new server.

It’s really hard to take calls to action like this seriously, when they unironically talk like this:

You cannot pass this invasive “browser check” without enabling JavaScript. This is a waste of five(or more) seconds of your valuable life.

Most of the other points are either grasping, misleading, or make the classic FOSS-centric assumption that we live in a fantasy land where all hosting is free and companies don’t need to exist.

I’m not out here trying to say Cloudflare is vital to society, but come on, these arguments are toothless.

I’ve seen people have similar issues on my issue tracker. Turns out it was caused by Cloudflare’s JS minimization or rocket-loader being enabled. Something changed in 0.18.3 that made it incompatible with those Cloudflare features. If you use the Cloudflare proxy to serve your site, you will need to turn those off.

Aw, thanks! :D