ole1986

how is it going with this feature!
Anything i can help with?

Dear agenciesfirst,

I am sorry to hear that you have issues with this plugin.
Of course not all parts are well documented as they exists due to some private rapid coding days.

Whenever I have time I can include more and more documentations. But time is also a problem as it has only 24 hours and my regular job uses a lot of it.

Anyway, if you want to get something pushed (like documentation for XXX) please feel free to raise an issue on github:

https://github.com/ole1986/wp-ispconfig3/issues

Also, fee free to improve it by doing a Pull Request at any time.
I will do a code review and can quickly integrate it, I promise!

@agenciesfirst

You may need to first select a customer.
And be sure its customer DOES match the user accounts being created on ISPconfig side.

The customer name is nothing else than the user, with “customer” role on wordpress as the plugins assumes it uses woocommerce to “order” a webspace, etc…

Things you may need to double check

* Have you already added a “clients on ISPconfig?
* Does this user have a website or database configured on ISPconfig?
* Does this client match a user account on wordpress side?
* Does this user have the Role “Customer”?

Regards,
Ole

Hi Tom,

Is the drop down menu from “websites” or “Databases” filled with the customers.

Also does the customer name have the identical name in ISPconfig?

Hi agenciesFirst,

* Open ISPConfig and add "wp-remote" (or any other) as 
  remote user under "System -> Remote Users"
* Give the user the following minimum access rights
  * Server functions
  * Record permission changes
  *  Client functions
  * Domaintool functions
  * Sites database functions
  * Sites Protected folder functions
  * Sites Shell-User functions
  * Sites Domain functions
* Open the "WP-ISPConfig3 -> Settings" and add the remote user 
  "wp-remote" with its password accordingly
* Also add the SOAP Location and URL the following
  * SOAP Location:  https://my.subdomain.tld/remote/index.php
  * SOAP Uri: https://my.subdomain.tld/remote/

If you do not have a valid certificate, use the “Skip certificate check” option to bypass it

Check possible error logs and report it here.

If you think this is a bug, please report to https://github.com/ole1986/wp-ispconfig3/issues

Thank you
Ole

• This reply was modified 7 years, 1 month ago by ole1986.
• This reply was modified 7 years, 1 month ago by ole1986.

@brody182

are you still having issue.
I would really appreciate to give me a more detailed feedback or at least remove this review.

Thank you

Hi @arnauddupont

usually it is shipped with two “default” registeration forms.

You can add this onto your page by using the shortcode:
[ispconfig class=IspconfigRegisterClient]
or
[ispconfig class=IspconfigRegisterFree]

when the form gets submitted it will register the username into wordpress and in the client section of ispconfig using the REST API.

So you need to make sure, that the REST API is properly configured in WP-ADMIN -> WP-ISPConfig3 -> Settings.

Do you receive any errors?

I will issue this on github to better track it

yes there is, it uses the soap client to fetch the Client templates from ISPConfig

’email’ is not yet a valid type – you can use ‘text’ instead.

I have selected the following under “Remote Users”

* Server functions
* Record permission changes
* Client functions
* Domaintool functions
* Sites database functions
* Sites Shell-User functions
* Sites Domain functions

Well, than the domain is already registered…
For testing purpose you can try some domain where NIC does not return a proper result.
Like: test.es

This should come up with: Domain properly unavailable (or something similar…)

If you agree I can test it from my machine by giving me the soap url and remote user / password combination.

To keep your data confidential, you can write me an email to: ole.k at web.de

Well, the ispconfig.php you are showing to me is not the original as it uses (for some unknown reason) $_POST['XXXXXXXX'] parameters instead of WPISPConfig3::$OPTIONS

So, i highly recommed to “reinstall” the plugin…

@wpmicronet

It must have something to do with the connection to the host.
So, please be very sure the address is properly entered in “WP-ISPConfig 3 -> Settings”:

SOAP Location:
https://yourserver:2053/remote/index.php in

SOAP URI:
https://yourserver:2053/remote/

Also make sure your certificate is valid when using HTTPS (SSL).

If you want to bypass the certificate verification you can try changing the file “ispconfig.php” in LINE 38:

public function withSoap(){
    $context = stream_context_create([
        'ssl' => [ 
            'verify_peer' => false,
            'verify_peer_name' => false,
            'allow_self_signed' => true
        ]
    ]);
    $this->soap = new SoapClient(null, [
        'location' => WPISPConfig3::$OPTIONS['soap_location'] , 
        'uri' => WPISPConfig3::$OPTIONS['soap_uri'], 
        'trace' => 1, 'exceptions' => 1, 
        'stream_context' => $context
    ]);
    $this->session_id = $this->soap->login(WPISPConfig3::$OPTIONS['soapusername'], WPISPConfig3::$OPTIONS['soappassword']);
        return $this;
    }

• This reply was modified 7 years, 11 months ago by ole1986.
• This reply was modified 7 years, 11 months ago by ole1986.
• This reply was modified 7 years, 11 months ago by ole1986.

@wpmicronet

At least it should show you an “empty” page returning status code 200.
You can check it from the following page:

https://httpstatus.io/

Just put https://subdomain.domain:2053/remote/index.php into it and press submit.
Result should be Status Code 200