-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 internal server error when adding 'promoter' #62
Comments
Bump :( |
I've stopped using Promoter over this :( |
Same here, one of our presskit() page stopped working. After looking around, it seems loading the XML file from Promoter is problematic. Everything runs fine on a local server, but once it's uploaded to our web hosting it stops working. I enabled the error display with
And this is what I got:
Apparently our web hosting server can't verify Promoter's SSL certificate. PHP 5.6 now verifies the peer's certificate by default when using SSL (see: http://php.net/manual/en/migration56.openssl.php). I don't have access to this configuration on my side, so I'll write a support ticket to my hosting provider. Promoter might have updated its SSL certificate, or enabled HTTPS redirection in the past months. Or maybe our hosting provider (and yours/your server) updated to PHP 5.6 recently. Cheers! |
I am adding the following to the bottom of my already existing and implemented data.xml for my game project, before
This causes that particular project page not to load with 500 internal server error. I checked the error_log and there is nothing that isn't normally there (PHP Warning: Module 'zip' already loaded in Unknown on line 0).
Do I need to reinstall the press kit and enable a particular setting? I have changed a number of links from http to https within sheet.php (things like youtube embed or the j-query library links), however even removing that/implementing it for the Promoter line made no change:
$promoterxml = simplexml_load_file('https://promoterapp.com/dopresskit/'.$promotercode);
Thanks,
Vicky
The text was updated successfully, but these errors were encountered: