Jump to content

ashevillewebhosting

Members
  • Content Count

    15
  • Joined

  • Last visited

About ashevillewebhosting

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ashevillewebhosting

    Error 1023 - Plesk Onyx - NAT

    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. 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) Add entry for 'hostname' to all addModuleRow() functions in plesk.php 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. 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!
  2. ashevillewebhosting

    Error 1023 - Plesk Onyx - NAT

    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.
  3. ashevillewebhosting

    Plesk NAT'd IP

    Revised... Realized Blesta was provisioning the subscription using the dedicated IP, which obviously wont work for more than one site... I changed the private IP address from shared to dedicated, and removed the public IP/NAT from it's settings. I then set the the public IP entry from dedicated to shared. Blesta now provisions to the shared public IP... and all appears to be happy? If anyone has any insight, comments, etc. regarding this setup let me know... really hoping to be able to deploy Blesta in the coming days!
  4. ashevillewebhosting

    Plesk NAT'd IP

    Hi, So after reading the thread below, I thought I'd give this a shot... My issue was that my Plesk Onyx server used a single shared NAT'd IP. In Plesk, I had set the public IP via the IP Addresses page. This has worked fine when provisioning in Plesk directly. However, Blesta provisioning would throw the error above if I used anything (hostname, public IP) other than the local private IP. I added a second IP in Plesk, using the same public IP as the private was NAT'd too, and set it as dedicated. I left the original private/public as shared. I then set the server to use the public via Blesta's Plesk Module/Add Server, and retested the provisioning... This time, I was able to create the customer AND provision the domain via Blesta without error. The login link for the client now works (minus the SSL warning). So I have two questions I guess... 1. Network/DNS experts... any issues you can foresee with this IP config in Plesk? (screen shot attached) 2. Is there a way to define public/private yet in Blesta, or even better hostname, which is easier to secure with an SSL cert?
  5. ashevillewebhosting

    Plesk NAT'd IP

    Hello, Currently trialing Blest for use with my Plesk hosting business, and really liking it thus far! One issue I ran into is that in order for Blesta to provision a package, I seemingly have to use the private IP address of the server in the Plesk Module, otherwise, while it will create the customer, I get the following error with trying to create the package/subscription in Plesk: domain.com <?xml version="1.0" encoding="UTF-8"?> <packet version="1.6.9.1"> <webspace> <add> <result> <status>error</status> <errcode>1023</errcode> <errtext>Unable to get ip id by address 'domain.com' from db.</errtext> </result> </add> </webspace> </packet> If I use the private IP, it works fine, however; from the Client portal the login link now uses this IP address, which is obviously not reachable for them. Any idea how I can overcome this? I really like the idea of being able to provide that login info to the client... one less question I have to field from them!
  6. ashevillewebhosting

    Plesk 17.8.11 Help

    Thanks Paul, That's what I was thinking, but I created another Plesk vm and installed a Blesta trial on it as well, and it worked fine when querying itself. Well, it pulled the packages from it; but I then saw the issues you mention above when provisioning a new account. I'm at a loss as to why that initial server won't output a response when querying packages, no matter whether Blesta is local or not. It's the only one out of 5 Plesk VMs that isn't working.
  7. ashevillewebhosting

    Plesk 17.8.11 Help

    Thanks all for your help on this. I'm really hoping to switch to Blesta if I can figure it out! So I spun up another Centos/Plesk VM, installed Blesta, and connected it via Plesk Module to the the two previous servers, as well as itself. This time I had no issues with packages on the same server, but continued to get no response from the initial problem server. Looking like it's less of a Blesta/Plesk thing, and more of an issue with that particular server just not outputting a response? Anyone know where I should be looking now? Any Plesk experts out there? These all have the same configurations essentially; same version OS, same version Plesk, same updates, etc.
  8. ashevillewebhosting

    Plesk 17.8.11 Help

    I tried this as well; stop using (systemctl stop firewalld) but same with the same result it seems.
  9. ashevillewebhosting

    Plesk 17.8.11 Help

    I went back and added the lines mentioned above... when adding the line below, server 1 (blesta locally installed) still doesn't work, and doesn't output error, server 2 works fine. $this->log($module_row->meta->ip_address, $response->raw(), 'output', false); When adding the below to 2260, same for server 1, server 2 no longer works. // Response is only an array if there is more than 1 result returned Dev tools output for server 1: module_email_tags:"{module.ip_address} {module.port} {package.type} {package.plan} {package.reseller_plan} {service.plesk_domain} {service.plesk_username} {service.plesk_password} {service.plesk_webspace_id}" module_options:"↵<div class="title_row"><h3>Module Options</h3></div>↵<div class="pad">↵ ↵ <ul>↵ <li>↵ <label for="module_group">Server Group</label>↵<select name="module_group" id="module_group">↵<option value="select">-- Please Select --</option>↵<option value="" selected="selected">Any</option>↵</select>↵ </li>↵↵ <li class="module_row_field">↵ <label for="module_row">Server</label>↵<select name="module_row" id="module_row">↵<option value="1" selected="selected">VPS1</option>↵<option value="2">VPS2</option>↵</select>↵ </li>↵ <li>↵ <label for="plesk_type">Account Type</label>↵<input type="radio" name="meta[type]" value="standard" id="plesk_type_standard" checked="checked" />↵<label for="plesk_type_standard" class="inline">Standard</label>↵<input type="radio" name="meta[type]" value="reseller" id="plesk_type_reseller" />↵<label for="plesk_type_reseller" class="inline">Reseller</label>↵ </li>↵ <li>↵ <label for="plesk_plan">Plesk Service Plan</label>↵<select name="meta[plan]" id="plesk_plan">↵<option value="" selected="selected">-- Please Select --</option>↵</select>↵ </li>↵ </ul>↵↵ <script type="text/javascript">↵ $(document).ready(function() {↵↵ // Bind tooltips for this content↵ $('#module_group').closest('ul').blestaBindToolTips();↵↵ // If no group selected hide row listing↵ ↵ // If group changes, determine if row listing should be shown↵ $('#module_group').change(function() {↵ if ($('#module_group').val() != "")↵ $('li.module_row_field').hide();↵ else↵ $('li.module_row_field').show();↵ })↵ });↵ </script>↵ ↵ <script type="text/javascript">↵ $(document).ready(function() {↵ $('input[name="meta[type]"]').change(function() {↵ fetchModuleOptions();↵ });↵ });↵ </script>↵ </div>↵" Name Dev tools output server 2: PleskResponse Object ( [xml:PleskResponse:private] => SimpleXMLElement Object ( [@attributes] => Array ( [version] => 1.6.9.1 ) [system] => SimpleXMLElement Object ( [status] => error [errcode] => 1014 [errtext] => Parser error: Request is invalid. Error in line 2: Element 'get': This element is not expected. Expected is one of ( owner-id, owner-login, owner-all ). ) ) [xml_container_path:PleskResponse:private] => /packet/service-plan/get [raw:PleskResponse:private] => error 1014 Parser error: Request is invalid. Error in line 2: Element 'get': This element is not expected. Expected is one of ( owner-id, owner-login, owner-all ). )
  10. ashevillewebhosting

    Plesk 17.8.11 Help

    Hi all, I was able to revisit this yesterday using a fresh install, this time adding both by Plesk servers in the module. I was able to add packages and provision accounts without issue when selecting the server that Blest ISN'T running on; however when selecting the same server as previously mentioned, which Blest IS running on, I ran into the same issue (no output in the logs). These servers are identically configured, so I'm assuming it has to do with the location of the install... any ideas? Thanks, Justin
  11. ashevillewebhosting

    Plesk 17.8.11 Help

    With that at 2260, or above the private function line, I just get a blank screen when trying to access the modules or packages page.
  12. ashevillewebhosting

    Plesk 17.8.11 Help

    I updated the file as described, but the modules log looks the same to me?
  13. ashevillewebhosting

    Plesk 17.8.11 Help

    Thanks Tyson, The Tools > Logs > Modules doesn't seem to be much help, I just have the same entry repeated (attached). Not sure where to look next.
  14. ashevillewebhosting

    Plesk 17.8.11 Help

    Thanks for writing back! The credentials are good, and the module logs just say 'success'. I did have an open_basedir error in blesta general-warning-2018-08-23.log, so I set it to none. I'm seeing this in the general-notice-2018-08-23.log: [2018-08-23 20:56:12] general.NOTICE: E_NOTICE: Trying to get property of non-object {"code":8,"message":"Trying to get property of non-object","file":"/var/www/vhosts/ashevillewebhosting.net/httpdocs/blesta/components/modules/plesk/plesk.php","line":2261} Are they're any unique firewall ports to be opened? This instance is running on the same server I'm trying to set up in blesta if that helps.
  15. ashevillewebhosting

    Plesk 17.8.11 Help

    Hi, I just installed Blesta 4.3.1 on my Plesk web server to give a try. I used the following guide to install the module and add new packages: https://docs.blesta.com/display/user/Plesk However, when I go to add a new package, the 'Plesk Service Plan' dropdown never seems to populate? Anyone out there familiar with this or how to fix it? Thanks! Justin
×