Closed VerlooveMaxime closed 3 months ago
Hi @VerlooveMaxime
I've no problem with that combination. What type of host you are using?
Hello @tinect
Nothing unsual. Normal stack with Nginx and MySQL. Just found out that accessing Adminer.php directly works. Going via the administration throws a 403 on the admin/adminer route.
Hi @VerlooveMaxime
to be sure: accessing admin#/frosh/adminer/list
throws a 403? In the iframe? Please share a screenshot.
Accessing Adminer.php
: so you downloaded them into a public folder of shopware and accessed them?
@tinect Not really. The admin/adminer route throws the error:
The login route works, so fetching the db credentials from the env variables works.
Googling 403 errors with Adminer shows some issues with creating sessions, looking in your code that is exactly what's done in that route. However, nothing has changed on server level regarding the php sessions. Same folder and permissions are used.
Yeah, copying Adminer.php to the public folder and accessing it directly works. I can login there with db credentials.
@VerlooveMaxime do you have any specific Security-Headers set on your hosting? Could you please verify, if it's happeing after the require or before (by shopware) by uncommenting this require?
@tinect Nothing about the hosting setup has changed since SW 6.4 and the plugin was working fine in that version. Commenting the require part loads the page just fine.
While we cannot reproduce this issue in any way, we need to close this issue here.
Please create a new issue, whenever you could help us to reproduce the issue on any default way.
I have the same issue. @VerlooveMaxime did you solve it from your side?
Unfortunately not. It's really weird because we have multiple clients that we upgraded from 6.4 to 6.5 and it only happened to one of them. As a workaround we copied adminer.php to a publicly accessible folder and logged in that way. Then we removed the adminer file again once done.
On Tue, Jul 2, 2024, 13:38 Markus Petritz @.***> wrote:
I have the same issue. @VerlooveMaxime https://github.com/VerlooveMaxime did you solve it from your side?
— Reply to this email directly, view it on GitHub https://github.com/FriendsOfShopware/FroshPlatformAdminer/issues/20#issuecomment-2202911277, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBVNROPFXJ3ZRSBQFF7UDA3ZKKGJ7AVCNFSM6AAAAAA5C7HP5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBSHEYTCMRXG4 . You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the response. I noticed the same... Especially because a direct clone of the shop on the same server works like a charm. @tinect would you be willing to check the issue directly on the client shop? Thanks
@petritz feel free to contact me in slack of shopware.
PHP Version
8.2
Shopware Version
6.5.5.2
Actual behaviour
Upgraded to SW 6.5.5.2 and the FroshPlatformAdminer plugin to 1.0.0. Also upgraded to php 8.2. After upgrading, opening Adminer shows an error message: "Session expired, please login again.". Entering the password does nothing.
What I have tried:
Expected behaviour
Expected to see the contents of the database instead of the login screen. Or at least for the login to work.
Steps to Reproduce?
Upgraded the store to SW 6.5.5.2 and the FroshPlatformAdminer plugin to 1.0.0.