aleph-im / aleph-proxy Goto Github PK

A secure connection between the two would be great.

The path to delete was:

/var/lib/docker/containers/7164d15533584278bc15a89f54932c42c255e14809afdcae34ae994556692d20/7164d15533584278bc15a89f54932c42c255e14809afdcae34ae994556692d20-json.log

The load balancer availability is only measured on IPv4.

Adding support for custom user domains in the load balancer would be useful for many users.

Let's Encrypt makes it possible to handle the obtention of TLS certificates on the load balancer.

This functionality would however require the development of a custom middleware that resolves the custom domain to the Aleph VM identifier registered on the domain via a DNS TXT record.

regarding these =>
https://github.com/aleph-im/aleph-proxy/blob/main/aleph_proxy_config/config.yaml#L50
https://github.com/aleph-im/aleph-proxy/blob/main/aleph_proxy_config/config.yaml#L57

to-aleph-vm:  # Forward VM calls to all available Compute Resource Nodes in the network
  rule: "PathPrefix(`/vm/`)"
  service: aleph-vm
  middlewares:
    - retry-if-no-reply
...
  middlewares:
    retry-if-no-reply:
      retry:
        attempts: 4
        initialInterval: 5ms

as we know, it is almost never safe to retry a request that alters a state

https://doc.traefik.io/traefik/routing/entrypoints/#http3

I cannot connect to aleph.cloud or official.aleph.cloud using the Mullvad Socks5 proxies. Connecting via the VPN works fine, except when going through the proxy of the VPN node.

Test with curl -vv --socks5-hostname 10.64.0.1:1080 https://aleph.cloud