Skip to content
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

connection mysql error #17

Open
leiviton opened this issue Dec 23, 2018 · 6 comments
Open

connection mysql error #17

leiviton opened this issue Dec 23, 2018 · 6 comments

Comments

@leiviton
Copy link

Sun Dec 23 00:31:23 BRST 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification."

a user indicated this link, but I could not identify the solution to the error, where I put useSSL = false?

https://cenote-issues.atlassian.net/browse/JAS-116

@hondaman900
Copy link

Did you manage to resolve this? I have an identical issue with same error.

PHPJasper-laravel is working great on my XAMPP localhost, but after deploying to Digital Ocean using Forge I get this same error as you when trying to execute a report. I can't find any solution, and adding the suggested "?useSSL = false" workaround to the end of the URL does nothing to resolve this. My hosting environment uses Nginx, MySQL and JRE8. My project is in Laravel 5.5. I also have an SSL certificate installed.

The rest of my project runs fine and uses the same connection string as phpjasper to access the MySQL database, but my app has no such issues, only the phpjasper execution.

Any assistance with this is very much appreciated.

@leiviton
Copy link
Author

leiviton commented Mar 11, 2019

I did not get it, I believe that this lib was abandoned, this problem occurs in the recent versions of mysql, as I did not receive a return for this issue and have nothing to do with it, I just gave up using it and found this https://github.com/Jimmy-JS/laravel-report-generator, maybe useful for you too

@hondaman900
Copy link

Thank you for the quick reply, but this is truly disheartening. I had tried unsuccessfully to get the cossou/JasperPHP package to work, but this one did, and worked well at least on my local dev XAMPP server. This issue only popped up when I deployed to a hosted server. My problem is I need Jasper as I've invested a ton of work in designing and building many reports with Jasper Studio.

I hope someone else reads this and can assist or identify the issue.

Thanks again for the reply.

@hondaman900
Copy link

I solved this by setting the host parameter to include the useSSL=false, since you can append it to the URL as recommended everywhere as the solution. I do this in my env file (I keep my Jasper parameters in the env file so that I can easily change them)

JASPER_DB_HOST=127.0.0.1&useSSL=false

Hope this helps someone else.

@leiviton
Copy link
Author

good night! great, putting that way just call in the report setup?

@ismendoza
Copy link

I solved this by setting the host parameter to include the useSSL=false, since you can append it to the URL as recommended everywhere as the solution. I do this in my env file (I keep my Jasper parameters in the env file so that I can easily change them)

JASPER_DB_HOST=127.0.0.1&useSSL=false

Hope this helps someone else.

Thank you,
Your solution didn't work for me, but I tried other way, this works for me 'database' => 'databasename?useSSL=true',

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants