[solved] remoting/soap without SSL? on dev VM.

Discussion in 'Installation/Configuration' started by niemand-glaumy, Mar 13, 2022.

  1. Sers!
    I am trying to use the remoting client on a local VM (ubuntu 20) with fictional domains (domain.ngfr). This means I can not get a SSL certificate. Sadly, SOAP displays me an error ("SOAP Error: Could not connect to host") when I try to use the example/login.php
    The soap_config.php should be set up correctly (it works on my live system) but neither https nor http (shows a bad gateway error) locations work. Not with localhost (didn't work at all, not even on live.), not with, not with domain.ngfr (domain works on live).

    I checked phpinfo(), SOAP is enabled.
    Username fits, Password fits as well; I changed it thrice now, just to make sure.

    So will I need to go through the hustle of creating a self signed cert (any simple tutorial links plz?) or is there a workaround for this? :)

    Edit: I tried setting "exceptions => 0" in login.php, here's the echo:
    Logged successfull. Session ID:SoapFault exception: [HTTP] Could not connect to host in /var/www/clients/client2/web6/web/import/login.php:16 Stack trace: #0 [internal function]: SoapClient->__doRequest() #1 /var/www/clients/client2/web6/web/import/login.php(16): SoapClient->__call() #2 {main}
    Logging out: Logged out.
    Last edited: Mar 13, 2022
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    niemand-glaumy likes this.
  3. till

    till Super Moderator Staff Member ISPConfig Developer

  4. Thanks!

    Here, I rewrote your Documentation site:

    Why? Because I was annoyed of it being eyeburn-white - and my "dark reader" plugin not being able to work with it, so I wrote a quick php page. It most likely can be immensely optimized but we don't do that here. :p

    Downside: This makes it not really usable - locally, as it needs to be hosted on a phpable machine.
    But on the Upside!
    A) It's more beautiful - no more oldschool frameset shenanigans (who does that!?)!
    A2)lso more beautiful: Dark page. No more eyes-burning-out when you switch over from p*hub in the middle of the night. ;)
    and B) more useful for those that document.
    C) easier to edit because I used external CSS (see "./css/style.css" and "./css/articlestyle.css")

    Function is:
    There is an "articles" directory, in which I put all of the original .html files from the "API-docs" directory. I made PHP glob through that directory and display all the files as navigation links.
    When clicked, a get value is submitted and the page content is displayed/included into the "content" container.
    This means: Every new "article".html that is dropped into the "articles" directory will automatically be listed and clickable.

    There's one more tiny issue: Somebody used inline CSS in a few lines of those article files. Bad no no! >:O
    And I won't be the one cleaning THAT up. :p
    But I could not see any issues in my short little test. So you just remove those when you find issues.

    Another change: the "Home" button on the left got turned into an ISPC-Logo. Dunno how that happened, bug maybe? But I won't question a working system. :p

    This is the DL link: https://floh.zone/uplds/ispc/API-docs-nmnd.zip

    I hope this is useful to you in any way. If it is not, don't worry, at least it is for me, as my eyes will be spared. And to update, I simply need to replace the current article files. :3
    Last edited: Mar 14, 2022
    ahrasis likes this.

Share This Page