2.6 is bug reporting feature broken ?

[dleigh]

Just upgraded to 2.6 and wanted to report a bug and got this error stack trace when I submitted it:

Erreur de communication de l'API avec: /api/issues

Erreur du texte: Unable to reach the issue bridge
Trace de Pile:

[
"#0 /home/ejadmin/sites/churchcrm/api/routes/issues.php(8): ChurchCRM\Service\SystemService->reportIssue(Object(stdClass))",
"#1 [internal function]: Closure->{closure}(Object(Slim\Http\Request), Object(Slim\Http\Response), Array)",
"#2 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/Handlers/Strategies/RequestResponse.php(41): call_user_func(Object(Closure), Object(Slim\Http\Request), Object(Slim\Http\Response), Array)",
"#3 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/Route.php(325): Slim\Handlers\Strategies\RequestResponse->__invoke(Object(Closure), Object(Slim\Http\Request), Object(Slim\Http\Response), Array)",
"#4 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\Route->__invoke(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#5 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/Route.php(297): Slim\Route->callMiddlewareStack(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#6 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/App.php(443): Slim\Route->run(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#7 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/MiddlewareAwareTrait.php(116): Slim\App->__invoke(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#8 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/App.php(337): Slim\App->callMiddlewareStack(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#9 /home/ejadmin/sites/churchcrm/vendor/slim/slim/Slim/App.php(298): Slim\App->process(Object(Slim\Http\Request), Object(Slim\Http\Response))",
"#10 /home/ejadmin/sites/churchcrm/api/index.php(56): Slim\App->run()",
"#11 {main}"
]

[crossan007]

@dleigh does your server block php curl? Are there any weird outbound firewall rules on your server?

The issue reporting feature requires your server to be able to communicate with the ChurchCRM demo servers.

This error would come from https://github.com/ChurchCRM/CRM/blob/master/src/ChurchCRM/Service/SystemService.php#L359

[dleigh]

The quick answer is that it has worked just fine before - the only "before" being "before 2.6". No changes to the environment that I know of since it did work. My environment is a shared hosting service (o2switch) in France.

Can you give me the url that it's contacting and I can see if I'm able to actually contact it from the command line when I ssh into my account?

[crossan007]

Issue submissions are an HTTP POST to http://demo.churchcrm.io/issues

an HTTP GET to http://demo.churchcrm.io should be sufficient to tell if the "plumbing is working"

[dleigh]

ejadmin@dong [~]# wget http://demo.churchcrm.io
--2017-03-12 20:45:26-- http://demo.churchcrm.io/
Resolving demo.churchcrm.io... 143.95.37.84
Connecting to demo.churchcrm.io|143.95.37.84|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html'

[ <=>                                   ] 13,749      --.-K/s   in 0.04s

2017-03-12 20:45:27 (354 KB/s) - `index.html' saved [13749]

Looks to be ok from that perspective.

[crossan007]

Have you confirmed this issue again since you reported it 5 days ago?

[dleigh]

Good call. It worked now:

Successfully submitted Issue #2106

So is this something that might just happen from time-to-time and I need to keep trying or did something change?

[crossan007]

We were having some DNS issues a few days ago . Can't be sure if that's the root cause or not.

I've never had an issue submission fail across 3 instances of CCRM.

[dleigh]

On my side, I'm on a shared server and I know that there are some less-than-scrupulous people with whom I share the server, as witnessed by the fact that our access to MailChimp gets blocked at an IP level by Akamai from time-to-time. Don't know if github or the Churchcrm hosting provider also might be blocking my IP address.

I guess we'll just find out the next time I need to try it.
Thanks!