Services give me an...
 
Notifications
Clear all

Services give me an error after upgrading to 1.2.1

22 Posts
3 Users
0 Reactions
4,416 Views
Posts: 29
Topic starter
(@bijan-pouya)
Eminent Member
Joined: 8 years ago

As you see the conversation on top, I had a problem with the servers after updating, and I manage to fix with your help, now when I try to make new hosting space with one of my hosting plans that error happens, all hosting plans have same server which is my virtual server. I can`t find anything related to hosting spaces in  PackageServices and ServiceItems.

I want to fix my old hosting spaces, I don`t have a problem with my old package

Reply
Posts: 1967
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

PackageServices and ServiceItems are the database tables that show you exactly what Service ID's are used for existing hosting spaces aswell as newly created ones.

Since you mentioned new ones work, but old ones are broken that would always be my first starting point to compare what Service ID's it's actually using.

as the most logical explanation is: their using different Service ID's, where old is using Service ID's currently not working / not working server, and newly created ones most likely uses different Service ID's which are working / on a working server.

Once you compared Service ID's you can verify which server and which service ID is being used by the newly created working ones, vs the old broken ones using the services table (or verify it from the url in configuration --> Servers for each configured service in the url they have ServiceID= )

Reply
Posts: 29
Topic starter
(@bijan-pouya)
Eminent Member
Joined: 8 years ago

I found the problem, the problem was in hosted organization, I Update that service and now just when I tick automatically hosted organization provision that error happens, after all would you explain me about this, what is domains per organization? when I have one plan with 4 websites (for example) I have to set 4 organizations and 1 domain per each or just 4 organizations and 0 domain? I really appreciate for your help.

Reply
Posts: 1967
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Glad you found it.
it still seems something is off between the space / hosting plan / server if you still get the error sometimes in specific situations tho. (automatic provisioning shouldn't be an issue).

 

For the domains: There's different type of domains, for example:

System --> domains: This is the global domains for pretty much everything, so in your example with 4 websites you put a minimum of 4 there.

Hosted Organization --> Domains per Organization: This is the amount of domains accepted by exchange (In Exchange --> Accepted Domains)
for example you can set 4 system domains and 1 org domain --> it means the Exchange emails can only accept mail from 1 domain.  If you set Domains per organization to 4, it can have 4x accepted domains in exchange, which means you can assign additional domains on the same exchange account, or exchange accounts with user@domain1.com user@domain2.com etc.

Reply
Posts: 29
Topic starter
(@bijan-pouya)
Eminent Member
Joined: 8 years ago

So many Thanks, What about organization without Domain per Organization? (domain per organization set to 0), is this organization still can accept mail as itself?

As you answer all of my questions, could you please answer this one that no one else answer anymore?

https://solidcp.com/forum/question/createaccount-fault-whmcs-module/

I really thank you again.

Reply
Page 3 / 5
Share: