Forum

Ask, reply and learn. Join the community of Akaunting.

New Discussion

Wizard Error first run

Ramin   ( User )

Commented 2 years ago

Hi All,
I use Softaculous and installed the software, upon login, asks for API country, etc after get to Tax info just pups up Opes something went wrong and looks like in a loop. Any help will be appreciated.

Muchlis   ( User )

Commented 2 years ago

error first run, server.php and index.php not found

Anne Pajon   ( User )

Commented 2 years ago

Hi. Same issue here like Ramin. Any ideas on how to solve this issue?

Ff   ( User )

Commented 1 year ago

Exact same issue than Ramin here. Unable to finish the wizard.
The browser console says : Impossible to load « https://akaunting.my-domain.fr/1/wizard/finish ». Un service worker a communiqué un objet « promise » à FetchEvent.respondWith() qui a renvoyé une valeur « undefined » qui n’est pas un objet « Response ».

Anne Pajon   ( User )

Commented 1 year ago

Hi. I am re-installing akaunting from scratch and facing the same issue again, any ideas on how to solve this issue?

Itzik   ( User )

Commented 1 year ago

I got it installed on my server with PHP 8.25 and all dependencies. But it gets stuck at /counting/1/wizard with a white screen and the trace of a mountainscape in the background. Now what?

Nnq Nnq   ( User )

Commented 1 year ago

same with me:
I got it installed on my server with PHP 8.2 and all dependencies. But it gets stuck at /counting/1/wizard with a white screen and the trace of a mountain scape in the background. Now what?

Regeneration Resources   ( User )

Commented 9 months ago

@Nnq Nnq

have you managed to solve your problem?

Leonardo Ahumada   ( User )

Commented 8 months ago

I got the same problem, after uploading the zip file to my server, I started the wizard, company name, currency, then nothing more.
I got the messenge, something went wrong.

I pressed the F12 button to se what the server responded, ERROR 403 FORBIDDEN ACCESS.

The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.

This status is similar to 401, but for the 403 Forbidden status code, re-authenticating makes no difference. The access is tied to the application logic, such as insufficient rights to a resource.

I checked the status for the files, it was 644, so I changed the permission of the files to 744 and it solved the issue.

Nnq Nnq   ( User )

Commented 8 months ago

Yes, the issue with in web server, I use now Nginx and it works OK

Please login or register to leave a response.

Showing 1 to 10 of 11 discussions