Caddy never stops

Help
3

This means you probably have another web server running on your machine using port 80. Turn that off so Caddy can use it.
This means Caddy is already running (or something else already using port 2019). Caddy uses this for its admin endpoint.

Yes, thanks, I followed you and restarted everything, clean sheet.

Keep in mind that doing --from localhost:5043 will try to set up Caddy to run with HTTPS (because Caddy is HTTPS by default), which means it will try to also set up automatic HTTP->HTTPS redirects, which uses port 80.

Yes this is what I want.
The server has his own self-signed certificates (from mkcert) and can run http2.

I am not trying to serve files. I am pushing SSEs from servers to clients in the browser so I want a continuation between the browser and back-end servers through Caddy, all along with http2.
The backend server only responds at https://localhost:4043/sse, not to http://localhost:4043 for example.

I can run caddy start --config Caddyfile and I can caddy stop. Good!

> caddy run --config Caddyfile

# Caddyfile
:5043 {
	reverse_proxy /sse 127.0.0.1:4043/sse
}
...
Successfully started Caddy (pid=9212) - Caddy is running in the background

Caddy listens on 2019 and on port 5043 (same PID as per lsof -i:)

However when I curl to 5043/sse, it don’t get the expected response:

> curl https://localhost:5043/sse

*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 5043 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number
* Closing connection 0
curl: (35) error:1400410B:SSL routines:CONNECT_CR_SRVR_HELLO:wrong version number

I understand that I is some resolving issues and may need a proper server name. Probably need more knowledge.

At least I found two articles in the wiki, this one and that one.