lookup api.loophole.cloud: no such host

[DarKWinGTM]

Registering your domain... Error! Post "https://api.loophole.cloud:443/api/site": dial tcp: lookup api.loophole.cloud: no such host 7:18PM ERR Something unexpected happened, please let developers know 7:18PM FTL Post "https://api.loophole.cloud:443/api/site": dial tcp: lookup api.loophole.cloud: no such host

[0x7f]

Hey @DarKWinGTM, I was just trying whether enabling IPv6 in the loophole backend will break anything. And yes, it did. You were very quick to notice. I already reverted it and loophole should be working normal again. Can you confirm?

[DarKWinGTM]

Hey @DarKWinGTM, I was just trying whether enabling IPv6 in the loophole backend will break anything. And yes, it did. You were very quick to notice. I already reverted it and loophole should be working normal again. Can you confirm?

Thanks for very fast reply. But on my side still not conenct to tunnel.

[0x7f]

It might be that your DNS provider is caching the broken entries for a little longer. The TTL for the DNS record was set to just 1 minute and should be gone since ~15 minutes already. Can you try resolving api.loophole.cloud on your end?

% dig +short api.loophole.cloud 8.8.8.8
138.201.126.72
% curl https://api.loophole.cloud
{"version":"0.0.1"}%

[0x7f]

Here the confirmation that loophole cli works for me:

% loophole path .
Loophole - End to end TLS encrypted TCP communication between you and your clients

There is new version available, to get it please visit https://github.com/loophole/cli/releases/tag/1.0.
Registering your domain... Success!
Starting local file server Success!
Starting local proxy server...  Success!
Initializing secure tunnel...  Success!

Forwarding https://REDACTED.loophole.site -> .
Press CTRL + C to stop the service
Logs:
1:33PM INF Awaiting connections...
1:33PM INF Succeeded to accept connection over HTTPS
1:33PM INF Succeeded to accept connection over HTTPS
1:33PM INF Succeeded to accept connection over HTTPS
1:33PM INF Succeeded to accept connection over HTTPS

[DarKWinGTM]

curl https://api.loophole.cloud

dig +short api.loophole.cloud 8.8.8.8
>
curl https://api.loophole.cloud
curl: (6) Could not resolve host: api.loophole.cloud

[0x7f]

@DarKWinGTM that's very strange that Google DNS (8.8.8.8) is not resolving it for you. Did it change in the meantime?

When using some website to resolve the endpoint, it works as well: https://dnschecker.org/all-dns-records-of-domain.php?query=api.loophole.cloud&rtype=ALL&dns=google (A record must be available for IPv4 to work and AAAA for IPv6 should not be set):

[DarKWinGTM]

@DarKWinGTM that's very strange that Google DNS (8.8.8.8) is not resolving it for you. Did it change in the meantime?

When using some website to resolve the endpoint, it works as well: https://dnschecker.org/all-dns-records-of-domain.php?query=api.loophole.cloud&rtype=ALL&dns=google (A record must be available for IPv4 to work and AAAA for IPv6 should not be set):

Now it's back, thanks you.

[DarKWinGTM]

Please help me, I get this error red flag, when i trying to get data from api. This is a data i want to get {"code":200,"data":{"content":{"code":200,"data":{"gbpReferenceNo":"gbp108571106780699","price":"650.00","qrcode":"00020101021230830016A00000067701011201150105560068127340218000000230317012055031800016789983140005053037645406650.005802TH5910GBPrimePay63049721","referenceNo":"167899831400050","resultCode":"00","resultMessage":"Success"},"error":"","text":"okay"},"request":"<Response [200]>","rescode":200},"text":"okay"}

On Sun, Mar 12, 2023 at 9:03 PM Maximilian Haupt @.***> wrote:

@DarKWinGTM https://github.com/DarKWinGTM that's very strange that Google DNS (8.8.8.8) is not resolving it for you. Did it change in the meantime?

When using some website to resolve the endpoint, it works as well: https://dnschecker.org/all-dns-records-of-domain.php?query=api.loophole.cloud&rtype=ALL&dns=google (A record must be available for IPv4 to work and AAAA for IPv6 should not be set):

[image: image] https://user-images.githubusercontent.com/176090/224549628-ea9059e0-a92d-4386-9e00-4793dfc72fb5.png

— Reply to this email directly, view it on GitHub https://github.com/loophole/cli/issues/218#issuecomment-1465208266, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCNBOICGNIS5W6N5WXQK5DW3XJUDANCNFSM6AAAAAAVYCTRNI . You are receiving this because you were mentioned.Message ID: @.***>

[DarKWinGTM]

8:38PM ERR TLS Certificate failed to provision. Will be obtained with first request made by any client, therefore first execution may be slower

Do you know what problem this message, No response from tunnel.

[0x7f]

Hi @DarKWinGTM we had an issue with our servers and just fixed them. It should work again. Please let me know if you are still running into issues.

[DarKWinGTM]

Hi @DarKWinGTM we had an issue with our servers and just fixed them. It should work again. Please let me know if you are still running into issues.

Thanks you, alot.

[DarKWinGTM]

2:58PM ERR Request ended with status code 500 2:58PM ERR Internal server error 2:58PM ERR Details: Something unexpected happened, please let developers know 2:58PM ERR Please fix the above issue and try again 2:58PM FTL Request Error (500): Internal server error - Something unexpected happened, please let developers know

[Morishiri]

@DarKWinGTM please try again now. We had a node failure at night.

[DarKWinGTM]

@DarKWinGTM please try again now. We had a node failure at night.

Thanks you for help. Lastest error message is.

Registering your domain... Error! Post "https://api.loophole.cloud:443/api/site": x509: certificate has expired or is not yet valid: current time 2023-03-29T16:52:54+07:00 is after 2023-03-29T08:40:23Z 4:52PM ERR Something unexpected happened, please let developers know 4:52PM FTL Post "https://api.loophole.cloud:443/api/site": x509: certificate has expired or is not yet valid: current time 2023-03-29T16:52:54+07:00 is after 2023-03-29T08:40:23Z Loophole - End to end TLS encrypted TCP communication between you and your clients

Hope, you found this error.

[DarKWinGTM]

6:34PM ERR Request ended with status code 500 6:34PM ERR Internal server error 6:34PM ERR Details: Something unexpected happened, please let developers know 6:34PM ERR Please fix the above issue and try again 6:34PM FTL Request Error (500): Internal server error - Something unexpected happened, please let developers know

[0x7f]

@DarKWinGTM which exact command did you use to start your tunnel? Will look into it and come back to you

[DarKWinGTM]

loophole http 8000 localhost --hostname NAMESUBADDRESS

I used this command without any change for over 3 month.

[DarKWinGTM]

Linux xubuntu.

[Morishiri]

@DarKWinGTM 500s should be gone now :)

[DarKWinGTM]

Seem now it's fine thanks you.

[DarKWinGTM]

Initializing secure tunnel... Error! ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain 12:07PM INF SSH Connection failed, retrying in 10 seconds... (Attempt 1/5) Initializing secure tunnel... Error! ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain 12:07PM INF SSH Connection failed, retrying in 10 seconds... (Attempt 2/5)

[DarKWinGTM]

Initializing secure tunnel... Error! ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain 10:10AM INF SSH Connection failed, retrying in 10 seconds... (Attempt 1/5)

[Morishiri]

Hello.

The issues should be resolved. Please try again.