We run 3 separate SolidCP installations across our companies. 2 of these have a top level domain configured to allow customer spaces to add subdomains. This was working fine until we upgraded to 1.4.2 a few weeks ago. Now when we attempt to add a provider subdomain to a customer’s account, it doesn’t work.
No error is returned when you click the Add Domain button. You are simply returned back to the form. It does not matter whether you check either the Enable DNS or Create Preview Domain boxes. I don’t see anything happening when I check the audit log either, making me think this is more of a UI problem. When you click the Add Domain button, the browser sends a POST to:
While I was upgrading one of our installations, I moved the Enterprise Server and Portal components to a new server, which never had either of these components on it before, so I know that the portal content is clean.
Has anybody else seen this issue?
I have not seen or heard of this issue before.
but i would check a few things:
- In hosting plan –> system –> do you have “Disable Tenant To Create Top-Level Domain:” unchecked?
- are all components (portal, enterprise, servers) upgraded properly?
- Try a iisreset / browser in incognito mode to make sure no files are stuck in cache.
I just checked all of those items.
None of my hosting plans have “Disable Tenant to Create Top-Level Domain” enabled.
All components pull up as version 1.4.2 and the database Versions table includes version 1.4.2. I did directly upgrade two of my databases from 1.4.0 to 1.4.2, but for one of them, I applied the updatedb.sql script from version 1.4.1 before applying the 1.4.2 version. All three of my installations have the same issue.
I reset IIS on all servers in my smallest installation which just has two servers and logged into the portal using a Chrome guest window. The problem still existed.
There does appear to be an issue with Provider Sub-domains being assigned. I have logged a bug for this. At this time i dont have an ETA on a fix but have linked this forum post for the developer to ask for any updates needed.
despite, the upgrade to 1.4.3 (all modules), i’ve still the same problem.
Error 503 with 1.4.2 & 1.4.3 .
Error 503 generally indicates an issue with ur application pool (stopped)
if you started it, and it stopped again (resulted again in an error 503) it’s usually due to username/password used (identity).
You should be able to find this in your event viewer application log as to why it stops.
stop & start the application pool of the Enterprise Server,
stop & start the application pool of the Portal
stop & start the application pool of the Server
, with the same problem.
There is an error messages in the event viewer application & in the Application section.
How could i send you this long error message ?
Did you verify after loading the site (again) any of the application pools is stopped?
If so which one. (as basically you can start/stop application pools but if they got an auth error they will stop again the second you load the site).
- Views1174 times
- Answers9 answers