Forum

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

New Discussion

Installation "stuck" on step 2, no errors

Jove   ( User )

Commented 3 years ago

Hello, I can't get past step 2, there are no errors. It looks like it doesn't complete the DB migrations. Each time I check the database it has created a few tables. If I go and refresh the page and continue again on the step 2 it will create a few more tables then stop.

Where do I begin?

Jove   ( User )

Commented 3 years ago

Looking over the tables, it does run thru it all, and it just creates duplicates the rest of the time with a new prefix.

Jove   ( User )

Commented 3 years ago

Does anyone have any clues? The install guide is quite lacking and the only reason I have gotten this far is that I write Laravel, but there are so much custom things here that I don't understand, like that the main index file is in the root for some reason.

Jove   ( User )

Commented 3 years ago

It was a DNS problem.. the server did not manage to resolve the IP of the DB server, so only some parts worked.

Tasos   ( User )

Commented 3 years ago

Hi Jove,

Please can you provide any further details?

I have the same issue at the database setup setp (2). I had the feeling that was routing problem since I had installed akaunting under htdocs/subdirectory.

Jove   ( User )

Commented 3 years ago

It was a DNS issue. Wrong DNS used so it didn't manage to lookup the server.
The window did however never change. Had to manually enter the new URL to go to step 3.

Tasos   ( User )

Commented 3 years ago

I have the same issue but my sql server is on localhost so DNS is not applicable to me.

Thank you anyway

Tasos   ( User )

Commented 3 years ago

I changed the window manually to third step as you suggested and completed normally the setup. It seems to work for now.

Thanks Jove!

John Brand   ( User )

Commented 3 years ago

I had similar problems progressing from step 2 to step 3 and decided to change two things on the install - after *many* attempts at re-installing.

Firstly, I changed the database server from 'localhost' to '127.0.0.1' and secondly I changed the admin password. The interesting thing is that it is possibly the second thing I tried that could have been the real issue. The first password I was using I realised (after I managed to get it to install correctly!) did not conform to the database policy's complexity rule. I wouldn't have thought that would make a difference though, as I would have assumed that the admin password is only stored in the database, not dependent on it. So, short answer is, it could be either of these things. When I have some more time I might try installing again to work out which it actually was. Hoefully it will help someone else out in the meantime

Uniprax   ( User )

Commented 2 years ago

I am giving up as there is not response from support or any solution to this issue.

Please login or register to leave a response.

Showing 1 to 10 of 11 discussions