Hi, there was an upstream outage
🔔 This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
Edit
Hi, there was an upstream outage
Hi, none of those IPs belong to us, were able to trace to your host ok. ICMP loss in middlebox is normal, 0% loss to your host.
We plan to support it in the future, there is one missing piece
Yes those offers are no longer available as we have run out of IP space
Very sorry about the terrible outage today, please check status page here https://lnvps.pages.dev/status
Sold out
I dont think we have an MSS issue with lnemail, even with a really low MSS it still doesnt connect, unless on your side its forcing the MSS higher than the actual path MSS between us.
Should be ok now, PMTU isnt very reliable (on certain paths), takes a while to learn mss, and if youre on debian it tries fancy post quantum crypto which is too big for even 1500 mtu so its almost always dropped
Seems like its maybe a debian image issue, i just tested on a clean ubuntu vm and it works first try, checking debian.. ``` ubuntu@VM1160:~$ curl -v https://deb.debian.org/debian/extrafiles | more % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host deb.debian.org:443 was resolved. * IPv6: 2a04:4e42:f::644 * IPv4: 199.232.58.132 * Trying [2a04:4e42:f::644]:443... * ALPN: curl offers h2,http/1.1 } [5 bytes data] * TLSv1.3 (OUT), TLS handshake, Client hello (1): } [512 bytes data] * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Server hello (2): { [122 bytes data] * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): { [1 bytes data] * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): { [19 bytes data] * TLSv1.3 (IN), TLS handshake, Certificate (11): { [2716 bytes data] * TLSv1.3 (IN), TLS handshake, CERT verify (15): { [264 bytes data] * TLSv1.3 (IN), TLS handshake, Finished (20): { [36 bytes data] * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): } [1 bytes data] * TLSv1.3 (OUT), TLS handshake, Finished (20): } [36 bytes data] * SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / RSASSA-PSS * ALPN: server accepted h2 * Server certificate: * subject: CN=cdn-fastly.deb.debian.org * start date: Jan 1 01:02:30 2026 GMT * expire date: Apr 1 01:02:29 2026 GMT * subjectAltName: host "deb.debian.org" matched cert's "deb.debian.org" * issuer: C=US; O=Let's Encrypt; CN=R12 * SSL certificate verify ok. * Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Connected to deb.debian.org (2a04:4e42:f::644) port 443 * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://deb.debian.org/debian/extrafiles * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: deb.debian.org] * [HTTP/2] [1] [:path: /debian/extrafiles] * [HTTP/2] [1] [user-agent: curl/8.12.1] * [HTTP/2] [1] [accept: */*] } [5 bytes data] > GET /debian/extrafiles HTTP/2 > Host: deb.debian.org > User-Agent: curl/8.12.1 > Accept: */* ```
Added to the backlog, none of our hosts support TEE as far as i can see, needs newer CPU's
Hosting KVM in Ireland on our own hardware and network.