Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Sorry I don't know then. Without some debug logs its uncertain what happens there. I need some info that is not anynomized so theres no mistakes due to wrong omissions.
- Check your DNS, does "nslookup yoursubdomainname" really resolve to the IP address of the OPNsense?
- If Yes, Whats the output of "curl -v subdomainname"
- What do the debug logs show when you try to reach it?
- Which kind of application is listening there? Is it a HTTP or HTTPS application.
- If the application demands a HTTPS connection, did you enable "TLS Insecure Skip Verify" like I asked?
- When you deactivate the handler for the subdomain AND disable "abort", do you at least see an empty webpage and the certificate?
If its a very complex issue, you can also go to https://caddy.community and fill out their help template. Show your old nginx configuration, and your current Caddyfile. That way they can see if theres a mistake.
You have enabled TLS, does that mean your internal service has a globally trusted certificate? Because if not, you need to make sure Caddy trusts the certificate.
Check this out, it explains it: https://docs.opnsense.org/manual/how-tos/caddy.html#reverse-proxy-the-opnsense-webgui
Otherwise, disable both TLS options you have set, and enable "TLS Insecure Skip Verify", it will skip certifocate handling and the internal HTTPS connection will "just work".
# DO NOT EDIT THIS FILE -- OPNsense auto-generated file
# caddy_user=root
# Global Options
{
log {
include http.log.access.6a100fb9-863d-4a8e-a6dc-6aaad5598184
output net unixgram//var/run/caddy/log.sock {
}
format json {
time_format rfc3339
}
}
email *email*
grace_period 10s
import /usr/local/etc/caddy/caddy.d/*.global
}
# Reverse Proxy Configuration
# Reverse Proxy Domain: "ef64738b-136e-4bba-b267-f6307990db7b"
domain.tld {
tls /var/db/caddy/data/caddy/certificates/temp/66a3c470808dc.pem /var/db/caddy/data/caddy/certificates/temp/66a3c470808dc.key
handle {
reverse_proxy 127.0.0.1 {
transport http {
tls
}
}
}
abort
}
[u][b]
This section does not work[/b][/u]
# Reverse Proxy Domain: "6a100fb9-863d-4a8e-a6dc-6aaad5598184"
*.local.domain.tld {
log 6a100fb9-863d-4a8e-a6dc-6aaad5598184
tls /var/db/caddy/data/caddy/certificates/temp/66a26c37d9228.pem /var/db/caddy/data/caddy/certificates/temp/66a26c37d9228.key
@febd140e-6307-4080-8419-d1de0c6a23b2 {
host *.local.domain.tld
}
handle @febd140e-6307-4080-8419-d1de0c6a23b2 {
handle {
reverse_proxy *local 192 address*:port {
transport http {
tls
tls_server_name *.local.domain.tld
}
}
}
abort
}
@dbd15585-f172-4fbd-8524-13d6dcd351af {
client_ip local 192 address
}
handle @dbd15585-f172-4fbd-8524-13d6dcd351af {
}
abort
}
rm -f /var/db/aliastables/* && /usr/local/opnsense/scripts/filter/update_tables.py seems to have worked.Thanks for sharing!
I tried https version, but i got this error:
* Closing connection -1
curl: (3) URL using bad/illegal format or missing URL
I tried plain http:
Ambiguous output redirect.
curl -H 'Content-Type: application/json' -X POST -v 'http://USERNAME:PASSWORD@127.0.0.1/control/update'curl --insecure -H 'Content-Type: application/json' -X POST -v 'https://USERNAME:PASSWORD@127.0.0.1:443/control/update'