pim-community-dev icon indicating copy to clipboard operation
pim-community-dev copied to clipboard

Published 20 hours ago • verified publisher icon akeneo

Error Getting 500 Internal Server Error

Open sachinparmartot opened this issue 3 years ago • 8 comments

Hello Team,

I am trying to install akeneo PIM community edition in my Ubuntu Server my server is in AWS with 4v core CPU and 16 Gb Ram while i try to install akeneo i am getting bellow error.

Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

i have try to many time to install i have follow all steps as per official sites. here i have attach image please check and update me

i am waitting for your response

akeneo

sachinparmartot avatar Oct 18 '21 12:10 sachinparmartot

500 internal

While i check this site it will getting above error.

sachinparmartot avatar Oct 18 '21 12:10 sachinparmartot

when you do NO_DOCKER=true make dev the .env file change (i don't know the reason..) I had the same problem and fixed it like this : cp .env /root/envv NO_DOCKER=true make dev --> in another console, check the .env regulary via the command cat .env when you see the file change, do cp /root/envv ./.env (you have to be placed in the directory that contain the .env file)

After that, i block at the same point, err 500 and i have no answer at all .. can someone help?

centoyas avatar Oct 18 '21 15:10 centoyas

Hi @centoyas ,

Have you created a DB for Akeneo and added a valid database connection to the .env file?

There seems to be a problem when the Akeneo installation command is trying to connect to the database.

krishankantshandilya avatar Jan 17 '22 07:01 krishankantshandilya

Wow, its been a long time ago.. i dont remeber , i can try again and tell you but i remeber i had to cp my env file cause the script replaced it

centoyas avatar Jan 17 '22 07:01 centoyas

Yes, when we run the command NO_DOCKER=true make dev then it resets the env files so before running this command you should cp the env file and then before running the command check that the env file variables reset or not. If the variables are reset right after running the command then paste the contents of the copied env file data in the .env file between command is running.

krishankantshandilya avatar Jan 17 '22 09:01 krishankantshandilya

Yep dat was exactly what i did

centoyas avatar Jan 17 '22 15:01 centoyas

A better way would be to create another file called .env.local and overload your parameters there, this file won't be changed. The env file is overwritten during installation.

Legion-God avatar Sep 29 '22 18:09 Legion-God

Hello guys, finally, Have you find a solution for this problem ?

rmxnnkoko avatar Sep 22 '23 23:09 rmxnnkoko