search

andreapollastri / cipi

Install and manage your server like a pro! With Cipi you don’t need to be a Sys Admin to deploy and manage websites and PHP applications powered by cloud VPS.
https://cipi.sh
1.08k stars 223 forks source link

Getting 404 after install #391

Open andreekeberg opened 2 years ago

andreekeberg commented 2 years ago

I just installed Cipi on a clean VPS with the correct Ubuntu version etc., installation went fine and I was presented with the various credentials after completion like expected.

However no matter which URL I try to visit on the servers public IP (which was also correctly shown on the "Setup complete" step after installation), I am just presented with the default nginx 404 error page.

Doesn't matter if I try just the root endpoint which should take me to the login screen, or e.g "/api/docs" etc.

I've tried restarting nginx but that didn't help.

Not sure if there was any problems with creating some files/folders/symlinks as I'm not sure at which path I should expect Cipi to have been placed in, but I can see that both /var/www and /etc/nginx/cipi are completely empty.

andreapollastri commented 2 years ago

Hi! Thank you for the issue. What provider are you using?

andreekeberg commented 2 years ago

Hi @andreapollastri, thank you for the quick reply!

I'm using a KVM based VPS at a local provider here in Sweden called GleSYS.

Should be nothing out of the ordinary, I did choose their cheapest configuration just for testing but it should meet your requirements from what I can see.

Attaching some details about the server here:

server
andreapollastri commented 2 years ago

OK! Thank You for the information, I have checked Cipi on several VPS providers and it works without issues on main brands! Maybe this provider uses custom Linux repositories or similar! I will check an installation on it in next days! We have to understand if there is any not fatal error during installation process that corrupts the standard flow of Cipi initialization! In the meanwhile... I'm sorry for the inconvenience!

andreekeberg commented 2 years ago

@andreapollastri Thanks a lot! I'd be happy to help debugging if possible, are there any log files created during the install process that I could locate, or maybe something I could tell the installer to do if not, using some option or env value?

I would ask my provider but I doubt they are able to offer any support unfortunately.

Not sure if this helps in any way, but since you mentioned custom repositories I'm guessing that you're thinking maybe some alternative packages/versions could have been installed unexpectedly?

If that could be the case, I'm attaching the full output of apt list --installed here as well!

apt-installed.txt

pyro-code01 commented 2 years ago

I think this is the same problem i had with my installation, it seems some providers are running apt-get upgrade on first boot when you initiate vps. Try doing it like this.

  1. Wipe/reinstall 20.04
  2. As soon as system boots try apt-get update && apt-get upgrade
  3. Check if there is any errors

If you get error like the other process is using apt-get and its locked, try to wait a bit since its updating something in the background and then try again if it passes reboot the machine with "reboot" as root.

After the reboot try again apt-get upgrade if it says 0 packages or completes, install CIPI.

It seems that one some providers they install these packages on first boot and it conflicts with cipi install, cipi says its installed fine, however when you try to access panel you get 404!

Possible fix: Implement check in cipi installer if apt-get package installer is locked on the other process to interrupt the installation or wait for process to finish, but dont kill the process as it may be updating kernel (i did it and bricked the VPS, kernel panic).

Regards