Error 1023 - Plesk Onyx - NAT

[theone85ca]

Hello,

I'm getting error ...

1023 Unable to get ip id by address <PUBLIC IP> from db.

... with the Plesk module installed in Blesta. It seems like Blesta passes the customer information but gets stuck creating the domains etc in Plesk. I've posted on the Plesk forums too but I dont seem to be getting anywhere there. I should note that im setup on a Google Cloud Compute Engine so am NAT'd which im sure is the issue but I just can't seem to pin this one down.

[Paul]

I think we chat a bit earlier. It does sound like it's related to NAT, perhaps a conflict between the module and the public IP address. I found this regarding our competitor - https://forum-dev.sp.parallels.com/threads/plesk12-in-nat-mode-whmcs-error-1023.334334/

I don't know if it's related or not. I suppose it's possible if the server IP address, as added to the module configuration is being passed and set for the account IP. I'd have to look at the code to determine if that's what's happening. Do you have any logs under Tools > Logs > Module Log? You can click a row to expand it to show the raw input/output which may be helpful.

 

 

[theone85ca]

Hey Paul,

 

Yes we did. Thank you for your help.

Here's the failed log.

 

INPUT: SUCCESS

35.184.3.141|webspace:add
a:3:{s:7:"general";a:5:{s:4:"name";s:11:"nickwood.ca";s:10:"ip_address";s:12:"35.184.3.141";s:11:"owner_login";s:8:"nickwood";s:5:"htype";s:7:"vrt_hst";s:6:"status";s:1:"0";}s:7:"hosting";a:2:{s:10:"properties";a:2:{s:9:"ftp_login";s:8:"nickwood";s:12:"ftp_password";s:3:"***";}s:4:"ipv4";s:12:"35.184.3.141";}s:4:"plan";a:1:{s:2:"id";s:1:"7";}}

 

 

OUTPUT:FAILED

35.184.3.141
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.5.0">
  <webspace>
    <add>
      <result>
        <status>error</status>
        <errcode>1023</errcode>
        <errtext>Unable to get ip id by address '35.184.3.141' from db.</errtext>
      </result>
    </add>
  </webspace>
</packet>

 

 

 

I did make a little progress towards this. Plesk Onyx has NAT support built in. It automatically reads the local IP assigned to eth0 and just allows you to add the public IP. If I add another IP that's just the public one Blesta provisions everything fine. However, at that point its like the virtual hosts file isn't directing properly and all the domains just direct to the default Plesk page. It almost seems like this is a Plesk issue but considering the Blesta provided module doesn't seem to provisioning things when Plesk is setup correctly...

 

The Plesk Module isn't checking the IP it's been given against the one listed as 'IP Address' and not 'Public IP Address' is it?

 

Edited March 4, 2017 by theone85ca

[theone85ca]

Should I open a bug ticket regarding this?

[theone85ca]

Maybe I'm missing something here.

I have the two IP's setup in Plesk, the internal is set as a shared IP and the public as dedicated. The command 'plesk repair dns' runs without error. Blesta also now creates full accounts as it did in my previous post. However, the same situation is occurring. The accounts are created on the dedicated IP and not the shared one. This causes the domains to be directed to the default Plesk page regardless of the content of the httpdocs.

Was there a way to specify which IP should be used for hosting?

[theone85ca]

This setup, per your image doesn't seem to be working for me.

Everytime I register a new domain is automatically puts it on the public IP which then only displays the default page. So frustrating.

 

 

[Paul]

On 3/10/2017 at 5:18 PM, theone85ca said:

This setup, per your image doesn't seem to be working for me.

Everytime I register a new domain is automatically puts it on the public IP which then only displays the default page. So frustrating.

 

 

It looks like the 1st item in the list is using a private IP 10.128.x.x, which is mapped to a public IP 35.184.x.x? Is the public IP address a shared IP? If it's a shared IP, shouldn't it show the default page? Sorry if I'm not understanding, I'm assuming that by default page you mean the standard page that's show when accessing the IP address in a browser rather than the website's content that's usually displayed when accessing a shared IP rather than a dedicated IP. Or is that public IP address a dedicated IP? If it's a dedicated IP, and it only maps to 1 local IP, there may be some other issue going on with Plesk.

[theone85ca]

Looks awesome.

[theone85ca]

So... is this a Blesta issue then?

[luke_ins]

On 3/14/2017 at 2:58 PM, Nelsa said:

 

I'm testing modified plesk module with two fields for IP adress ,one field ip_adress and second public_ip:adress ..should be done very soon

Hello, 

 

Is an update available for this at all?
I'm testing Blesta at the moment for POC but have hit this stumbling block. 

If I set the public IP as dedicated I am able to add account to Plesk via Blesta, but then have to go to website settings to change the IP back to the shared pool for the site to work.
This is fine for POC but won't work for us in production.

Please let me know. 

[Blesta Addons]

i think they have completed the task to add plesk 12 and above , but not sure if this will be released as patch release or in the next major release

[luke_ins]

Hi, 

Thanks for the update, is there anywhere to see a roadmap to next release date or any info on the next releases?
This is not in production for us - POC stage, so if testing is required let me know. Be happy to beta test and provide feedback.

Kind regards

[Blesta Addons]

30 minutes ago, luke_ins said:

Hi, 

Thanks for the update, is there anywhere to see a roadmap to next release date or any info on the next releases?
This is not in production for us - POC stage, so if testing is required let me know. Be happy to beta test and provide feedback.

Kind regards

https://dev.blesta.com/browse/CORE-1771

[ashevillewebhosting]

On 3/14/2017 at 10:58 AM, Nelsa said:

 

I'm testing modified plesk module with two fields for IP adress ,one field ip_adress and second public_ip:adress ..should be done very soon

Hello - did you ever manage to come up with a solution for this? I'm dealing with the same issue and it's keeping me from being able to roll out Blesta into production.

[ashevillewebhosting]

Hello all,

I believe I may have found my solution; with the very kind help of Nelsa. Using the private IP in Blesta works fine; however my end goal was to replace the IP with the hostname so that the client could utilize the login feature with a secure URL instead of an invalid IP. 

1. Add field for hostname to add_row.pdt and edit_row.pdt in Plesk>Views>Defaut. (this would be a FQDN and secured for Plesk login)
2. Add entry for 'hostname' to all addModuleRow() functions in plesk.php
3. Edit admin_service_info.pdt & client_service_info.pdt in Plesk>Views>Defaut, replacing 'ip_address' with 'hostname'. This allows both client and admin to use login feature with secured FQDN.
4. Leave ip_address/ipv4 as is; seems to provision and work fine using the private IP, as long as I set the NAT public address in Plesk for said IP.

I'm no expert, just a network guy, so if there's something flawed here please let me know; seems to be working in my test environment. 

The one thing I haven't figured out; how to set the label name for  the 'hostname' field in the add/edit views. If anyone has some insight there I'd gladly appreciate it!

[Tiny]

What does happen, if you change the order of  the ip addresses? It just might use the first in list.

Alternative, assigning  different ports?

If you use NAT, you can use a dynamic IP and reserve it in DHCP for your server.

[Tiny]

"Plesk API xml request package for add:webspace has two fields for IP address...one is server ip and second is hosting account IP...this is logic because you may want to have different IP for hosting accounts......" 

Yes, but I assign static IPs after the account is created (cPanel)and I am not using a local IP, just the public one(s)

Unless you sit next to server, you should not need a private IP, and still, you can start it as normal.

[Tiny]

I think, that is done via ..../admin/settings/company/modules/manage/3/

Add a package just for server (x) and other for server (y)

Your packages might have names like admin_packageone .... and the other server nimda_packageone (depending on server name/IP ...

And if you group the servers, you should be able to run the same package name. I am not that long on Blesta, but my understanding is, one server = full, the next in the group ised. The you need the same  serer_package in both

[Tiny]

Why you want the server NATed? There is no real  reason for this.

Open up the router/firewall.

. iI am not expert in PHP, but with ssh AND NAT you might need to add/change different ports, if and when NATed. In PHP it might be similar, you might have to add a port to you IP? 

something like xxx.xxx.xxx.xx:2234 , to get to the other IP, because the standard port :22 is likely used for the local IP?

 

Sorry, your forum link does not work for me

[Tiny]

I know, plesk is very popular. So hundreds, if not more would search and ask for solution. That would have been fixed within hours or a few days. Also Blest is pretty popular. I doubt, you are the only one and then affected.

That must be something else, a simple setting or config issue, which nobody here notices.

I have a few servers with NAT, I just need them for my work, all VPS. I only connect via public IP, no local IP. I only can approach them via different ports, same as my staff, who are working on there, also me.

Different for different user groups and admins. ANd a similar config I would also would attempt with plesk, if you need NAT. I am sure, that pretty near, why you get the setups on the wrong IP