Hi Oliver, I found the error regarding rpc in the apache log:
Can't locate object method "boolean_values" via package "JSON::PP" at /usr/lib/cgi-bin/rpc.fcgi line 36. [Wed Jul 06 15:50:36.326729 2022] [fcgid:warn] [pid 22:tid 139795204400896] (104)Connection reset by peer: [client 172.18.0.1:52040] mod_fcgid: error reading data from FastCGI server [Wed Jul 06 15:50:36.326793 2022] [core:error] [pid 22:tid 139795204400896] [client 172.18.0.1:52040] End of script output before headers: rpc.fcgi Best Regards, Gordon Nicholas On Tue, Jul 5, 2022 at 10:58 PM Oliver Welter <[email protected]> wrote: > Hi Gordon, > > did you check the apache log? > > Oliver > On 05.07.22 11:53, Gordon Bin Nicholas wrote: > > Hi Oliver, > > Thanks for the help. > > Unfortunately, the problem still persists. It responded with the same > Internal Server Error - 500 and without writing to the rpc.log file. > However, the est.log and scep.log files get created when I call their > respective endpoints. Is there any other method I can use to access the > backend of OpenXPKI via HTTP/S? > > Best Regards, > Gordon > > On Thu, Jun 30, 2022 at 6:19 PM Oliver Welter <[email protected]> wrote: > >> Hi Gordon, >> >> welcome ;) >> >> You must add the name of the "endpoint" to the URI, the default config >> comes with two - public and enroll, so you need to call >> http://localhost:8080/rpc/public >> >> You will very likely find the error message in the apache server log as >> the rpc layer dies very early with the wrong url so the logging is not yet >> set up. >> >> Oliver >> On 30.06.22 16:59, Gordon Bin Nicholas wrote: >> >> Hi, >> >> I am interested in OpenXPKI and started an instance of it using docker >> following the instructions given on the github page for oepnxpki-docker. I >> configured the Apache server to accept RPC calls via HTTP port 8080. >> However, I ran into problems trying to call any of the RPC endpoints. For >> example, I called: >> >> curl -F "method=SearchCertificate" -F "common_name=test" >> http://localhost:8080/rpc >> >> The response: >> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> >> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server >> Error</h1> <p>The server encountered an internal error or misconfiguration >> and was unable to complete your request.</p> <p>Please contact the server >> administrator at [no address given] to inform them of the time this error >> occurred, and the actions you performed just before this error.</p> >> <p>More information about this error may be available in the server error >> log.</p> </body></html> >> I tried accessing rpc.log to find out what's wrong. But to my surprise, >> the log was never created. I tried calling the EST-Wrapper. This time it >> worked perfectly fine. Why does RPC give me an error, but EST works fine? >> Is there a misconfiguration for RPC? (The configuration I have is from the >> openxpki-config repository) >> Thanks and Regards, >> Gordon Nicholas >> >> >> _______________________________________________ >> OpenXPKI-users mailing >> [email protected]https://lists.sourceforge.net/lists/listinfo/openxpki-users >> >> -- >> Protect your environment - close windows and adopt a penguin! >> >> _______________________________________________ >> OpenXPKI-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/openxpki-users >> > > > _______________________________________________ > OpenXPKI-users mailing > [email protected]https://lists.sourceforge.net/lists/listinfo/openxpki-users > > -- > Protect your environment - close windows and adopt a penguin! > > _______________________________________________ > OpenXPKI-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openxpki-users >
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
