• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

domain stuff aggrivating the hell out of me

L

lordpsyan

Guest
my domain. samccstudios.com

I have now installed kubuntu 3 times, from scratch. set hostname as samccstudios.com the first 2 times, and samccstudios the third.

This is the **** Plesk gives me, and it keeps me from logging into plesk

first time I could log in. I would type www.samccstudios.com:8443
it would lookup localhost.localdomain:8443
couldn't connect on any other computer but locally.

second time (and I removed this from about 600 places, mostly config files)
it gave me samccstudios.com.com

third time, to remove one of the .com's I just put samccstudios as host name.

then I got samccstudios.sw.biz.rr.com

now why the hell won't it just give samccstudios.com?

I just want to be able to remove the monitor, keyboard and mouse from the server and do everything remotely. I would LOVE to start paying for the 100 domain license, but I am not getting anywhere. I had it running perfectly under centos5, but centos is a horrible OS (nopt as bad as the real redhat tho) and I wanted to keep debian, but thats another story. I want this to work. there is insufficient help online for these problems, and emailing tech support takes weeks to get a reply.

please, someone tell me how to define the fgdn, instead of letting it pick and choose for itself.

LP
 
Check /usr/local/psa/admin/conf/httpsd.conf (might also be /opt/psa/admin/conf depending on the version installed).

There should be a line in the <VirtualHost *:8443> that reads

ErrorDocument 400 https://localhost.localdomain:8443

Update that line to what you want your requests to http:// on port 8443 to redirect to. That should fix your problems.
 
Back
Top