Issue Unable to Access Servers via .plesk.page Subdomains

[danielgc]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

Plesk Obsidian 18.0.67 Update 3

Hi everyone,


I suddenly can't access some of my Plesk-managed servers using the .plesk.page subdomains. For example: nice-chaum.74-208-50-131.plesk.page. I can still access these servers via their IPs without any issues, but managing them through platform360.io was much more convenient. I checked the A records for these subdomains on dnschecker.org, and it seems they’re gone. Does anyone know what happened? Was there an official announcement about shutting down .plesk.page subdomains that I might have missed?

Thanks in advance for any insights!

 

[scsa20]

Those domains are meant to be only temporary and can be cleared at any moment. If you want an easy way of connect using DNS I would suggest updating it to use one of your own domains with a subdomain like I have mine set to panel.domain.tld.

Also I just did a dig and it still shows up for me

╭─ pwsh        22ms⠀                                                                                               8,18:46 
╰─ dig nice-chaum.74-208-50-131.plesk.page

; <<>> DiG 9.16.28 <<>> nice-chaum.74-208-50-131.plesk.page
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57051
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;nice-chaum.74-208-50-131.plesk.page. IN        A

;; ANSWER SECTION:
nice-chaum.74-208-50-131.plesk.page. 21560 IN A 74.208.50.131

;; Query time: 0 msec
;; SERVER: 192.168.2.51#53(192.168.2.51)
;; WHEN: Tue Mar 11 21:47:56 US Mountain Standard Time 2025
;; MSG SIZE  rcvd: 80

 

[danielgc]

Thx a lot, it seems they're unstable, I will use my own. Thx!

 

[Sebahat.hadzhi]

@danielgc there's currently a technical issue ongoing with the temporary domain names. Our team is aware and actively working on fixing it. At this point, I cannot provide an ETA. I cannot suggest a better alternative than @scsa20 's recommendation about using your own domain names for accessing the server.