hangs on starting server

[sikhaman]

Hello, I followed tutorial, attached my domain but after command I see

Starting server on <myadress>.adnl and thats it. I tried to reach website through mytonwallet or telegram and no luck. any ideas?

[xssnick]

Hi, if you see Starting server on it means it is started. The reason can be that port from config.json is not accessible for inbound UDP requests, maybe your IP is not public or you have some filtering like iptables.

[sikhaman]

Hello @xssnick,
with ufw I opened ports

To                         Action      From                             │
--                         ------      ----                             │
22/tcp                     ALLOW       Anywhere                         │
Nginx Full                 ALLOW       Anywhere                         │
12291/udp                  ALLOW       Anywhere                         │
22/tcp (v6)                ALLOW       Anywhere (v6)                    │
Nginx Full (v6)            ALLOW       Anywhere (v6)                    │
12291/udp (v6)             ALLOW       Anywhere (v6)                  

so what I did to check my port is opened. on my server I did

nc -u -l 12291

on my client side I did

nc -u <my.ip.add.res> 12291

After what on client side I send some text and saw its on server side. So I assume port is open and IP is public and open

However if I do command like

nmap -p 12291 -sU my_server_ip

I have a results like

Starting Nmap 7.95 ( https://nmap.org/ ) at 2024-08-08 10:26 EDT
Nmap scan report for myip.nl3.servers.guru (my ip)
Host is up (0.10s latency).

PORT      STATE  SERVICE
12291/udp closed unknown

Nmap done: 1 IP address (1 host up) scanned in 2.35 seconds

And rn it shows EVERYTHING is OK, Starting server on vttdzkmzos5am2afamuqmm2nixdco54dvreytjyad3ruhbs6etnowtq.adnl
So can it be like Network/ISP level filtering: my hosting provider or ISP might be blocking incoming traffic on this port?? Or any ideas?

[gelakhubutia]

I encountered a similar issue and observed the following:

If you're hosting multiple websites on the same server with regular domains (e.g., my-site.com) attached to your IP address, it may interfere with the .ton domain functionality. This appears to be the primary issue in my case, though I welcome confirmation or correction on this point.
Cache-related challenges:
After unlinking the domain and commenting out the relevant Nginx rules, the website with the attached .ton domain began functioning correctly. However, when attempting to reload the page in Telegram, only the old version was visible. Interestingly, I could see the changes using ton.run service, but not in Telegram.

Given these observations, I'm seeking advice on how to effectively manage caching issues. It's both inefficient and costly to repeatedly relink the domain and flush the cache. Are there any recommended strategies or best practices to address this caching problem more effectively?