Unable to add provi...
 
Notifications
Clear all

Unable to add provider subdomain on version 1.4.2

10 Posts
5 Users
0 Reactions
3,828 Views
Posts: 4
Topic starter
(@netsource)
New Member
Joined: 8 years ago

Hello,

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:

https://<url>/Default.aspx?pid=SpaceDomains&mid=75&ctl=add_domain_step2&DomainType=ProviderSubDomain&SpaceID=<spaceid>&ReturnURL=

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?

9 Replies
Posts: 1987
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

I have not seen or heard of this issue before.

but i would check a few things:

  1. In hosting plan --> system --> do you have "Disable Tenant To Create Top-Level Domain:" unchecked?
  2. are all components (portal, enterprise, servers) upgraded properly?
  3. Try a iisreset / browser in incognito mode to make sure no files are stuck in cache.
Reply
Posts: 4
Topic starter
(@netsource)
New Member
Joined: 8 years ago

Hello Marco,

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.

Reply
Posts: 5
 amir
(@amir)
Active Member
Joined: 8 years ago

Hi,

I have exact same issue. Is there any update?

Reply
Posts: 1493
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

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.

Thanks,

Trevor

Reply
Page 1 / 2
Share: