-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
You have unfortunately mis-interpreted the "Use SSL to connect to target" option. It's an easy mistake to make, what it's referring to is the connection from the client at the end of the tunnel to the "target" i.e. the HTTPS server. It's used for situations which have a site with a clearnet presence where you want to offer an I2P gateway, but don't want to put that gateway on the same server as the I2P router. So the proxy is doing the SSL connection, and not necessarily the browser. To see an example of how it can be used in this fashion, have a look at: https://mirror-github-pages-to-i2p.github.io In order to be able do HTTPS on your I2P site it's a little more complicated, I don't know that we have native support for it with the default i2ptunnel. sam-forwarder(the Go i2ptunnel) has it, and I can do a tutorial/writeup of how to use it soon. Most importantly have a look at https://github.com/s-rah/onionscan and related work before deploying http/2 and http/3, there is probably a safe way to do it but there is a reason our defaults in the Jetty server are very cautious.
Related posts
-
How to Manage Multiple Terraform Environments Efficiently
-
Building a gRPC Server with NestJS and Buf: A Comprehensive Showcase
-
OpenTofu v1.7: Enhanced Security with State File Encryption
-
Monitoring energy usage with smart plugs, Prometheus and Grafana
-
Take a look at traefik, even if you don't use containers