Trouble with IPv6 (was "HELP NEEDED URGENTLY") !!!

[matix131997]

@mmtrade

Yahoo rejects your emails due to fresh domain registration.
Some popular email blockers from 1 to 6 months depending on the domain tld. A good solution to this problem is to send from yahoo email, icloud, gmail etc to your own email.
Send a normal long text message once a day and you can't send in bulk to start with from your mail because then they will permamently block your IP address.
At my place with a .cloud domain, I had a problem receiving iCloud emails for six months.

On top of that, Contabo IP addresses are popular among e-mail providers as spam servers.

[mmtrade]

@matix131997 It does not deliver eitherway

I have tried to send from yahoo and it keeps bouncing back

@girish please share your ideas on this solution.

[AartJansen]

@mmtrade this is a yahoo issue
try contacting them about it
https://senders.yahooinc.com/contact/

[humptydumpty]

I’ll save you the trouble.. use an smtp relay like mailgun

[girish]

@mmtrade usually the IP addresses in most VPS providers are blocked by the big mail providers. You have to use a mail relay or be patient with warming up the IP for say 6 months or so (and contact the big providers to unblock your IP). There is no other solution to this.

[csteiger]

@girish I

I have the same problem since today. I can't install any app anymore, I get the "ipv6.api.cloudron.io unreachable" error.

ubuntu@s3:~$ curl https://ipv6.api.cloudron.io/api/v1/helper/public_ip
curl: (28) Failed to connect to ipv6.api.cloudron.io port 443 after 132362 ms: Connection timed out

A problem with your server? It doesn't answer to ping.

ubuntu@s3:~$ ping ipv6.api.cloudron.io
PING ipv6.api.cloudron.io(2604:a880:800:10::b66:f001) 56 data bytes
^C
--- ipv6.api.cloudron.io ping statistics ---
184 packets transmitted, 0 received, 100% packet loss, time 187390ms

Thanks in advance for your help.

[girish]

@csteiger the server is definitely up

$ ping ipv6.api.cloudron.io
PING ipv6.api.cloudron.io (2604:a880:800:10::b66:f001) 56 data bytes
64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=1 ttl=45 time=205 ms
64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=2 ttl=45 time=132 ms
64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=3 ttl=45 time=133 ms
64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=4 ttl=45 time=276 ms
64 bytes from prod.cloudron.io (2604:a880:800:10::b66:f001): icmp_seq=5 ttl=45 time=129 ms

Can you check your network? Are you able to ping other IPv6 addresses?

[csteiger]

@girish

Thanks.

I don't know what happened, the local DNS was down... a reboot did it

[mmtrade]

@girish my cludron server is offline..

i do not know why but no matter what i do and retsart it is still offline

[mmtrade]

[nebulon]

Is the DNS resolving to the correct IP? At least the one it resolves for me is not even pingable, so is that server publicly reachable?

[mmtrade]

@nebulon I checked in my cloudflare and i just readjusted the server DNS to the IP

It is still not working and i do not know why? what should I do from here?

[humptydumpty]

@mmtrade it could be because of DNS propagation, check it using an online tool: https://mxtoolbox.com/dnspropagation.aspx

[mmtrade]

https://mxtoolbox.com/supertool3?abt_id=AB-631A&abt_var=Variation&action=a:ronsteels.com:all

[mmtrade]

and yes i adjusted the IP on my cloudflare. I initaially rebooted my VPS and i think that was why the DNS changed. But i had to go to my cloudflare to adjust this also

[mmtrade]

so i corrected the issue with the DNS now.

[nebulon]

Is it working now? Is your dashboard domain resolving to the correct IP ? At least from here it appears to be resolving to an IP which is not reachable on any port I've tried.

[mmtrade]

it is not working... the domain is resolving to the correct IP but i cannot seem to open the cloudron at all

this is my vps IP 185.203.217.223

you can check from any tool to see if it is resolving fine. I think the problem is on cloudrun

can you advise

[matix131997]

I checked that your domains have the IP address you provided and it detects correctly, that is, the DNS is set correctly. The next test I did was a port scan and BUM. They are filtered. If you didn't set something with SSH some settings then Contabo restricted IP access to the server e.g.: a large number of requests or an attack on your servers e.g. SSH hacking attempt.

If you didn't have a secured server with a few parameters that restricts the attack on SSH in sshd_config with a public key then you really had hack attacks.
I too have 2 servers in Contabo and I didn't experience any attack because I already set up according to the security standard SSH access to the server right after launching the Cloudron platform.

The solution? You need to write to support to unblock the IP address, if not then change the address to another one and manually enter in Cloudflare the new address in each entry "A" and "AAAA"

[mmtrade]

@matix131997 I really would need some help chaning it manually. I have written the support and still no answer. I could use your help if you come on a live followup