-
After updating to the latest version (v6.3.3), I noticed that my assets only work if I add a / at the end. If I just click the link of any asset, it gives me the 404 Page not found error. As soon as I add the / at the end, it displayes the asset. I'm not an expert so please consider that when anwsering or asking addational questions. Also, I found something that said to try to run the php upgrade.php again and it returns this error.
Thank you in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Latest is actually 6.3.4 :) We didn't change anything in how URLs are parsed in recent versions, so I'm not sure why you'd be seeing that. |
Beta Was this translation helpful? Give feedback.
-
You can also upgrade manually - the upgrader just bundles up a bunch of commands that need to be run, so people don't accidentally miss a step.
Is there anything in your app logs that might indicate an issue somewhere else? |
Beta Was this translation helpful? Give feedback.
-
I was able to do the upgrade manually but had to add a step before composer install to upgrade composer. After that, the upgrade worked but the URL issue still exists. I did upgrade through several versions when I did the upgrades so was there a version somewhere back in the 4's or 5's that change URL parsing? Thanks! |
Beta Was this translation helpful? Give feedback.
-
I wanted to provide an update. After doing a bit more investigating, I realized that my URL actually had an extra / after the IP. So I went into my .env file and removed that from behind the IP, saved it and it's working again. |
Beta Was this translation helpful? Give feedback.
-
My .env file had APP_URL=http://x.x.x.x/ I removed the trailing / so now it shows APP_URL=http://x.x.x.x It is working again. |
Beta Was this translation helpful? Give feedback.
My .env file had APP_URL=http://x.x.x.x/
I removed the trailing / so now it shows APP_URL=http://x.x.x.x
It is working again.