The requested resource was not found.

shaokeyibb / flarum-passkey-login

Apache License 2.0

6 stars 1 forks source link

The requested resource was not found. #7

Open faisalnjs opened 2 months ago

faisalnjs commented 2 months ago

When attempting to use the plugin anywhere (signup, login, adding to existing account) the alert shows.

shaokeyibb commented 2 months ago

Hello, can you provided more error and context to me? Like the console log and your Flarum version

faisalnjs commented 2 months ago

The error happens whenever I click "Login with passkey" or "Add a passkey" or any other button for the extension. This is happening on mobile (iOS 17.8) and desktop (Windows 11). Flarum is running version 1.8.5 - latest, new install. Here is the error log:

shaokeyibb commented 2 months ago

Hello, I'm trying to reproduce your issue in my enviroment but it seems to all right...

I think it might be something wrong with your web server. Maybe you can provide the responseText in your screenshot and that may helpful to me.

faisalnjs commented 2 months ago

Here is the responseText:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<p>Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>

shaokeyibb commented 2 months ago

Hello faisalnjs, I'm trying to figure out why it's happened but looks like there's not a further progress to me. Maybe you can try to reinstall your plugin or clear the cache of your Flarum.

I will mark this issue as help wanted and hope there's any further people provided more information about the bug.

faisalnjs commented 2 months ago

Clearing Flarum cache, purging extension files, disabling & reenabling the extension, and uninstalling & reinstalling the extension did not work in my case.

When purging extension database entries and files, I disabled the plugin and then clicked the "Purge" button. It said it succeeded, but enabling back the extension still showed the entered Relying Party Name and Relying Party ID. Maybe that is part of the reason why?