Reverse proxy problem

Help
1

1. The problem I’m having:

i’m trying to do reverse proxy for my jellyfin server to acces it outside my network but when i run caddy it give my an error. for the dns i use noip service

2. Error messages and/or full log output:

2023/05/05 23:17:49.771 ERROR   http.acme_client        challenge failed        {"identifier": "alfi.ddns.net", "challenge_type": "http-01", "problem": {"type": "", "title": "", "detail": "", "instance": "", "subproblems": []}}
2023/05/05 23:17:49.771 ERROR   http.acme_client        validating authorization        {"identifier": "alfi.ddns.net", "problem": {"type": "", "title": "", "detail": "", "instance": "", "subproblems": []}, "order": "https://acme.zerossl.com/v2/DV90/order/zyEEZ0c3rXfVzSAFNQlVBQ", "attempt": 1, "max_attempts": 3}
2023/05/05 23:17:49.772 ERROR   tls.obtain      could not get certificate from issuer   {"identifier": "alfi.ddns.net", "issuer": "acme.zerossl.com-v2-DV90", "error": "HTTP 0  - "}
2023/05/05 23:17:49.772 ERROR   tls.obtain      will retry      {"error": "[alfi.ddns.net] Obtain: [alfi.ddns.net] solving challenge: alfi.ddns.net: [alfi.ddns.net] authorization failed: HTTP 0  -  (ca=https://acme.zerossl.com/v2/DV90)", "attempt": 1, "retrying_in": 60, "elapsed": 20.8758294, "max_duration": 2592000}

3. Caddy version:

v2.6.4 h1:2hwYqiRwk1tf3VruhMpLcYTg+11fCdr8S3jhNAdnPy8=

4. How I installed and ran Caddy:

a. System environment:

windows 11 pro build:22621.1555

b. Command:

cd C:\caddy
    caddy run

c. Service/unit/compose file:

d. My complete Caddy config:

alfi.ddns.net {
	encode gzip
    reverse_proxy localhost:8096 
}
 
 
# Edit 05/06/20 Remove Empty Brackets, Change logging format, and added Email portion. Commented out email portion for now
# Edit 05/07/20 Removed Email portion. Adding an optional part in the guide for it.
# Proof /u/NoFeedback4007 is original author. :)
# Edit 02/27/2023 Removed Log portion file

5. Links to relevant resources:

2

I’m unable to connect to your server at 87.3.16.65, so the ACME server is unable to as well. You’ll need to make sure your Caddy instance is reachable directly through that domain for it to be able to solve the challenge.

3

Since you’re on Windows, make sure Windows firewall allows connections on port 80 and 443 (both TCP and UDP).

Make sure your router’s port forwarding is configured to send traffic on those ports to your Windows machine.

We strongly recommend running Caddy as a Windows service, so it starts up with your machine Keep Caddy Running — Caddy Documentation (because Windows is obviously prone to randomly rebooting for updates when it feels like it).

4

now it says

2023/05/06 00:53:58.580 INFO    admin   admin endpoint started  {"address": "localhost:2019", "enforce_origin": false, "origins": ["//127.0.0.1:2019", "//localhost:2019", "//[::1]:2019"]}
2023/05/06 00:53:58.581 INFO    serving initial configuration
5

That’s all it says? Looks like you forgot to give Caddy your config file, or something like that.

6

now it works i tried to connect the server on my phone and its connecting but it give me some error

2023/05/06 09:01:25.065 INFO    http    enabling automatic HTTP->HTTPS redirects        {"server_name": "srv0"}
2023/05/06 09:01:25.066 INFO    tls     cleaning storage unit   {"description": "FileStorage:C:\\Users\\mate8\\AppData\\Roaming\\Caddy"}
2023/05/06 09:01:25.066 INFO    http    enabling HTTP/3 listener        {"addr": ":443"}
2023/05/06 09:01:25.066 INFO    http.log        server running  {"name": "srv0", "protocols": ["h1", "h2", "h3"]}
2023/05/06 09:01:25.067 INFO    http.log        server running  {"name": "remaining_auto_https_redirects", "protocols": ["h1", "h2", "h3"]}
2023/05/06 09:01:25.067 INFO    http    enabling automatic TLS certificate management   {"domains": ["alfi.ddns.net"]}
2023/05/06 09:01:25.077 INFO    tls     finished cleaning storage units
2023/05/06 09:01:25.086 INFO    autosaved config (load with --resume flag)      {"file": "C:\\Users\\mate8\\AppData\\Roaming\\Caddy\\autosave.json"}
2023/05/06 09:01:25.086 INFO    serving initial configuration
2023/05/06 09:03:49.901 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "http2: stream closed"}
2023/05/06 09:03:49.901 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "http2: stream closed"}
2023/05/06 09:03:58.721 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "http2: stream closed"}
2023/05/06 09:04:10.695 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "write tcp 192.168.1.83:443->37.161.240.190:46601: wsasend: An existing connection was forcibly closed by the remote host."}
2023/05/06 09:04:13.822 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "http2: stream closed"}
2023/05/06 09:04:38.361 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "http2: stream closed"}
2023/05/06 09:08:31.789 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "write tcp 192.168.1.83:443->37.161.240.190:46633: wsasend: An existing connection was forcibly closed by the remote host."}
2023/05/06 09:08:33.627 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "write tcp 192.168.1.83:443->37.161.240.190:46534: wsasend: An existing connection was forcibly closed by the remote host."}
2023/05/06 09:10:46.640 ERROR   http.handlers.reverse_proxy     aborting with incomplete response       {"error": "write tcp 192.168.1.83:443->37.161.240.190:46532: wsasend: An existing connection was forcibly closed by the remote host."}
7

idk if this are fine or i need to do something

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.