Jump to content
Froxlor Forum
  • 0
adamjedgar

Install on Google Cloud Compute LAMP - debian

Question

Hi guys,

 

I have a google cloud compute debian instance

I have been experimenting with a couple of alternatives to cpanel. Just installed virtualmin and now am looking at froxlor.

 

I have followed the install outline as documented.

1. I setup a google cloud launcher LAMP

2. navigated in browser to <myserveripadress> to ensure apache is working (which it is)

3. downloaded froxlor to /var/www/ directory

4. chown froxlor to www-data:www-data (i also checked to ensure my webserver is running as www-data)

 

Now when i attempt to navigate to http://<mywerveripadress>/froxlor i get the following error in browser 

"NOTFOUND" the requested URLwas not found on this server.

 

now when i ssh into server, froxlor is definatelly in /var/www/ directory.

permissions are  0755 www-data:www-data

 

i am not sure what i have done wrong?

 

has anyone with experience in installing this on google cloud got any advice?

Share this post


Link to post
Share on other sites

11 answers to this question

Recommended Posts

  • 2

And yet they go to all the trouble to write an install document...most people would expect said documentation to be up to date with the O/S its designed to run on. The additional directory added by debian happened quite a while ago...certainly plenty of time to update this.

In all honesty, a very quick and easy 2 minute change to the installation instructions could save many users lots of frustration.. and help retain client base instead of driving them away to better documented competing platforms.

Just get someone to update the document...i would do it myself if i had access to it. Its unfortunate that i found the answer to my problem on digital ocean's forum rather than here.

 

Share this post


Link to post
Share on other sites
  • 1
1 hour ago, davidoct14 said:

Hello I'm running a froxlor server on google cloud computers too. Do you have a problem with the mailling ports? thanks for your answer.

And you already openend another thread for this, 

So no need to hijack another thread

Share this post


Link to post
Share on other sites
  • 0

ah, i found the problem...i noticed that in another post on Digital Ocean's forum there was a mention that in ubuntu 14lts there is an additional level of folder for the web directory... /var/www/html.

The installation documentation i read on froxlor makes no mention of the new directory and as such i placed my froxlor directory and file inside /var/www/ .

When i searched the www directory i saw that it had an index.html file there and assumed this was the apached one, when apached actually has files inside the /var/www/html/ directory.

 

So for newbies...please ensure that when you are following the froxlor installation documentation, you download all froxlor files and folders to /var/www/html/ (not /var/www/ ).

then its just a matter of navigating in web browser to <yourwebserverexternalipaddress>/froxlor

(or if hostname has been set to domain name <yourdomain.com>/froxlor)

Share this post


Link to post
Share on other sites
  • 0
6 hours ago, adamjedgar said:

So for newbies...please ensure that when you are following the froxlor installation documentation, you download all froxlor files and folders to /var/www/html/ (not /var/www/ ).

then its just a matter of navigating in web browser to <yourwebserverexternalipaddress>/froxlor

(or if hostname has been set to domain name <yourdomain.com>/froxlor)

Froxlor presupposes strong user experience with your server system....

If you can't handle simple server configs without reading a how-to, it's better for you to use Plesk or something else like this...

...Same Shit Different Day...

  • Like 1

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, iam said:

Froxlor presupposes strong user experience with your server system....

If you can't handle simple server configs without reading a how-to, it's better for you to use Plesk or something else like this...

...Same Shit Different Day...

Well, I can understand his point and I think it would not be too much if some sort of note would be added to the install documentation.
I might submit a PR later.

Share this post


Link to post
Share on other sites
  • 0

another quickie whilst on topic...usually with some other programs one may edit the user (such as change admin password) using phpmyadmin.

I attempted to do this today and it doesnt appear to make any difference...ie its not working. 

 

Any suggestions?

Share this post


Link to post
Share on other sites
  • 0

well, depends on what hash-algorithm you set and what value you have used when manually playing around in the database....you know there is a "forgot password" function? which needs to be enabled for admin-users of course....

Also: i don't think other programs intend that you edit the user data via phpmyadmin...total nonsense

Share this post


Link to post
Share on other sites
  • 0
13 hours ago, d00p said:

well, depends on what hash-algorithm you set and what value you have used when manually playing around in the database....you know there is a "forgot password" function? which needs to be enabled for admin-users of course....

Also: i don't think other programs intend that you edit the user data via phpmyadmin...total nonsense

Hi dOOp,

thank you for your reply.

actually phpmyadmin is often used for editing database users in content management systems in particular...Wordpress being just one example where its extensively used for just this job as a fail safe when nothing else works (ie when the recover password option is not an option)

Anyway, take the following:

I install froxlor and use it for about 2 hours having logged in and out a few times during this time without issue. I havent set up everything as i am just testing the program, hence no password recovery option is enabled. I log off, go to bed, get up the next morning to find that the only password i ever use for all my installations is no longer working (how that happens i dont know but it has).

I now need to edit the user password manually to regain acess to froxlor without having to reinstall. My assumption is that the method would be, as i have done with Wordpress, use phpmyadmin to change the password directly in the database.

 

Is that how you guys would do it?

which hash algorythm is used for froxlor? (wordpress uses MD5)

Share this post


Link to post
Share on other sites
  • 0

Froxlor uses whatever you set in the settings. Default is SHA-256. If you want to reset it using phpmyadmin you can always set a MD5() password, froxlor will convert it on the first login.

Share this post


Link to post
Share on other sites
  • 0
On 8/4/2017 at 6:30 PM, adamjedgar said:

Hi guys,

 

I have a google cloud compute debian instance

I have been experimenting with a couple of alternatives to cpanel. Just installed virtualmin and now am looking at froxlor.

 

I have followed the install outline as documented.

1. I setup a google cloud launcher LAMP

2. navigated in browser to <myserveripadress> to ensure apache is working (which it is)

3. downloaded froxlor to /var/www/ directory

4. chown froxlor to www-data:www-data (i also checked to ensure my webserver is running as www-data)

 

Now when i attempt to navigate to http://<mywerveripadress>/froxlor i get the following error in browser 

"NOTFOUND" the requested URLwas not found on this server.

 

now when i ssh into server, froxlor is definatelly in /var/www/ directory.

permissions are  0755 www-data:www-data

 

i am not sure what i have done wrong?

 

has anyone with experience in installing this on google cloud got any advice?

Hello I'm running a froxlor server on google cloud computers too. Do you have a problem with the mailling ports? thanks for your answer.

Share this post


Link to post
Share on other sites
  • 0

Manually installing LAMP on a google compute engine is a long process. You have to install each package individually. You can easily install LAMP on google compute if you use PaaS services, like Cloudways. In this platform, the server is configure with PHP automatically.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Christian Vogel
      Ich habe Froxlor installiert und alle Konfigurationen ausgeführt. Dennoch kann ich nicht über Outlook oder Mail auf mein Imap Konto zugreifen. 
      Im syslog sehe ich
      Sep 10 10:11:51 vserver3130 dovecot: imap-login: Aborted login (no auth attempts in 0 secs): user=<>, rip=87.191.51.26, lip=109.73.50.135, session=<uGoEloF1eIxXvzMa>
      postconf -d und dovecot -n hab ich als Textdatei angehängt.
      Habe auch schon etwas bei Google gesucht und hier im Forum die Suchfunktion bemüht - finde aber keine Lösung. Kann mir hier jemand helfen? Werden noch andere Infos benötigt für eine Lösung?
      Danke
      Christian
       
       
      dovecot.txt
      postconf.txt
    • By AreYouLoco?
      Hi,
      I am trying to setup froxlor on my Debian LAMP. I followed the guide from here: https://github.com/Froxlor/Froxlor/wiki/Install-froxlor-on-debian and and here https://github.com/Froxlor/Froxlor/wiki/Install-froxlor-from-tarball.
      I am stuck on page that I need to provide credentials to the database. When I go forward I do get this:

      I fill in my credentials; new password for froxlor database, new password for admin account, my root password that I can use to login locally via:
      mysql -u root -p Please help

       
      EDIT:
      I did some research and I allowed remote root login.
      MariaDB [(none)]> show grants; +------------------------------------------------------------------------------------------------+ | Grants for root@localhost | +------------------------------------------------------------------------------------------------+ | GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED VIA unix_socket WITH GRANT OPTION | | GRANT PROXY ON ''@'%' TO 'root'@'localhost' WITH GRANT OPTION | +------------------------------------------------------------------------------------------------+  
    • By محمدرضا چاوشی پور
      Hi!
      I',m configure the system.
      I got into trouble when making the user and as the image above indicates that folder access is difficult and could not create the user in the system.
      please help me!
      tank you 
    • By shaaz
      Is that possible to install froxlor in c-panel using one database user password?
      Or how can we skip the values of mysql_unpriv_user and mysql_unpriv_pass while installing?
    • By stolly82
      Hallo zusammen, 
      ich bin immer sehr aktiv in Fehler selber lösen, aber aktuell bin ich an einem Punkt angekommen wo ich mittlerweile wirklich alle Beiträge im gesamten WorldWideWeb durchsucht habe und einfach nicht weiter komme :-( 
       
      Ich habe einen Debaian Jessie Server mit ein paar Kunde & Froxlor seit Jahren aktiv am laufen.
      Durch php7 und der Inkompatibilität einiger älterer Anwendungen benötige ich leider FCGID um auf einigen domänen noch die 5.x Version laufen zu lassen.
      Bei der Installation (mittlerweile nach knappen 15 Stunden mit google und Versuchen) scheitert es bereits an dem Punkt in der Anleitung:

       
      Das hatte ich vorher total übersehen, dass der Server dort anstatt 10001 etc. den Usernamen finde sollte. Demnach hatte ich bei der Installation weiter gemacht und bin immer bei dem Punkt hängen geblieben wo ich diese wunderschöne Fehlermeldung AH00543: apache2: bad user name **** bekommen habe.
      Ich habe bei Froxlor mittlerweile wirklich alle configs neu / plane aufgespielt und nscd will einfach die User nicht den ID´s zuordnen. 
      Was habe ich gemacht:

      Bei der Installation gibt es für mich auch keine erkennbaren Fehler. 
      Ich habe die MySQL Passwörter die ich bei Froxlor in die Config eingegeben habe selbstverständlich auch geprüft und testweise auch den root user / pw genommen. 
      Ebenfalls habe ich die Anleitung von hier genommen:
      https://github.com/Froxlor/Froxlor/wiki/apache2-with-fcgid
      Dort stimmte allerdings der Punkt mit dem 
      apt-get install libnss-mysql nicht mehr, da es mittlerweile libnss-mysql-bg ist. Demnach passten da auch die obersten beiden Config files nicht mehr.
       
      /etc/nss-mysql-root.conf /etc/nss-mysql.conf /etc/nsswitch.conf
       
      Hier mal das LOG File vom nscd.
       
      Vielleicht hat ja einer von euch eine Idee was das Problem sein könnte. 
       
      Danke und LG
       
      Jan 
       
      DAS WAR BEIM ERSTEM PLANE START: Fri 19 Jan 2018 06:51:51 PM CET - 17748: register trace file /etc/passwd for database passwd Fri 19 Jan 2018 06:51:51 PM CET - 17748: register trace file /etc/hosts for database hosts Fri 19 Jan 2018 06:51:51 PM CET - 17748: register trace file /etc/resolv.conf for database hosts Fri 19 Jan 2018 06:51:51 PM CET - 17748: register trace file /etc/services for database services Fri 19 Jan 2018 06:51:51 PM CET - 17748: register trace file /etc/netgroup for database netgroup Fri 19 Jan 2018 06:51:51 PM CET - 17748: cannot stat() file `/etc/netgroup': No such file or directory Fri 19 Jan 2018 06:51:51 PM CET - 17748: handle_request: request received (Version = 2) from PID 17749 Fri 19 Jan 2018 06:51:51 PM CET - 17748: INVALIDATE (passwd) Fri 19 Jan 2018 06:51:51 PM CET - 17748: pruning passwd cache; time 9223372036854775807 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYUID entry "0", timeout 1516384654 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYNAME entry "nobody", timeout 1516384745 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYNAME entry "root", timeout 1516384654 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYNAME entry "vmail", timeout 1516384746 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYUID entry "65534", timeout 1516384745 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYNAME entry "postfix", timeout 1516384745 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYUID entry "115", timeout 1516384745 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYUID entry "2000", timeout 1516384746 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYUID entry "116", timeout 1516384746 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETPWBYNAME entry "debian-spamd", timeout 1516384746 Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYUID entry "0" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYNAME entry "nobody" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYNAME entry "root" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYNAME entry "vmail" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYUID entry "65534" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYNAME entry "postfix" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYUID entry "115" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYUID entry "2000" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYUID entry "116" Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETPWBYNAME entry "debian-spamd" Fri 19 Jan 2018 06:51:51 PM CET - 17748: handle_request: request received (Version = 2) from PID 17758 Fri 19 Jan 2018 06:51:51 PM CET - 17748: INVALIDATE (group) Fri 19 Jan 2018 06:51:51 PM CET - 17748: handle_request: request received (Version = 2) from PID 17759 Fri 19 Jan 2018 06:51:51 PM CET - 17748: handle_request: request received (Version = 2) from PID 17759 Fri 19 Jan 2018 06:51:51 PM CET - 17748: INVALIDATE (hosts) Fri 19 Jan 2018 06:51:51 PM CET - 17748: pruning hosts cache; time 9223372036854775807 Fri 19 Jan 2018 06:51:51 PM CET - 17748: considering GETHOSTBYADDR entry "127.0.0.1", timeout 1516387746 Fri 19 Jan 2018 06:51:51 PM CET - 17748: remove GETHOSTBYADDR entry "127.0.0.1" Fri 19 Jan 2018 06:51:52 PM CET - 17748: handle_request: request received (Version = 2) from PID 17778 Fri 19 Jan 2018 06:51:52 PM CET - 17748: GETFDGR Fri 19 Jan 2018 06:51:52 PM CET - 17748: handle_request: request received (Version = 2) from PID 17778 Fri 19 Jan 2018 06:51:52 PM CET - 17748: GETGRBYNAME (vmail) Fri 19 Jan 2018 06:51:52 PM CET - 17748: handle_request: request received (Version = 2) from PID 17779 Fri 19 Jan 2018 06:51:52 PM CET - 17748: GETFDGR Fri 19 Jan 2018 06:51:52 PM CET - 17748: handle_request: request received (Version = 2) from PID 17779 Fri 19 Jan 2018 06:51:52 PM CET - 17748: GETGRBYNAME (vmail) Fri 19 Jan 2018 06:51:53 PM CET - 17748: handle_request: request received (Version = 2) from PID 17780 Fri 19 Jan 2018 06:51:53 PM CET - 17748: GETFDGR Fri 19 Jan 2018 06:51:53 PM CET - 17748: handle_request: request received (Version = 2) from PID 17780 Fri 19 Jan 2018 06:51:53 PM CET - 17748: GETGRBYNAME (vmail) Fri 19 Jan 2018 06:51:53 PM CET - 17748: handle_request: request received (Version = 2) from PID 17781 Fri 19 Jan 2018 06:51:57 PM CET - 17748: handle_request: request received (Version = 2) from PID 17793 Fri 19 Jan 2018 06:51:57 PM CET - 17748: GETPWBYUID (1) Fri 19 Jan 2018 06:51:57 PM CET - 17748: Haven't found "1" in password cache! Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "1" of type GETPWBYUID for passwd to cache (first) Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "daemon" of type GETPWBYNAME for passwd to cache Fri 19 Jan 2018 06:51:57 PM CET - 17748: handle_request: request received (Version = 2) from PID 17793 Fri 19 Jan 2018 06:51:57 PM CET - 17748: GETPWBYUID (102) Fri 19 Jan 2018 06:51:57 PM CET - 17748: Haven't found "102" in password cache! Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "102" of type GETPWBYUID for passwd to cache (first) Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "messagebus" of type GETPWBYNAME for passwd to cache Fri 19 Jan 2018 06:51:57 PM CET - 17748: handle_request: request received (Version = 2) from PID 17793 Fri 19 Jan 2018 06:51:57 PM CET - 17748: GETPWBYUID (115) Fri 19 Jan 2018 06:51:57 PM CET - 17748: Haven't found "115" in password cache! Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "115" of type GETPWBYUID for passwd to cache (first) Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "postfix" of type GETPWBYNAME for passwd to cache Fri 19 Jan 2018 06:51:57 PM CET - 17748: handle_request: request received (Version = 2) from PID 17793 Fri 19 Jan 2018 06:51:57 PM CET - 17748: GETPWBYUID (2000) Fri 19 Jan 2018 06:51:57 PM CET - 17748: Haven't found "2000" in password cache! Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "2000" of type GETPWBYUID for passwd to cache (first) Fri 19 Jan 2018 06:51:57 PM CET - 17748: add new entry "vmail" of type GETPWBYNAME for passwd to cache MITTLERWEILE BEKOMME ICH NUR NOCH DAS HIER: Fri 19 Jan 2018 07:47:02 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:02 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:02 PM CET - 31374: handle_request: request received (Version = 2) from PID 31496 Fri 19 Jan 2018 07:47:02 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:02 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:03 PM CET - 31374: handle_request: request received (Version = 2) from PID 31497 Fri 19 Jan 2018 07:47:03 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:03 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:03 PM CET - 31374: handle_request: request received (Version = 2) from PID 31498 Fri 19 Jan 2018 07:47:03 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:03 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:04 PM CET - 31374: handle_request: request received (Version = 2) from PID 31499 Fri 19 Jan 2018 07:47:04 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:04 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:04 PM CET - 31374: handle_request: request received (Version = 2) from PID 31500 Fri 19 Jan 2018 07:47:04 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:04 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:05 PM CET - 31374: handle_request: request received (Version = 2) from PID 31501 Fri 19 Jan 2018 07:47:05 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:05 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:05 PM CET - 31374: handle_request: request received (Version = 2) from PID 31502 Fri 19 Jan 2018 07:47:05 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:05 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:06 PM CET - 31374: handle_request: request received (Version = 2) from PID 31503 Fri 19 Jan 2018 07:47:06 PM CET - 31374: GETFDGR Fri 19 Jan 2018 07:47:06 PM CET - 31374: provide access to FD 8, for group Fri 19 Jan 2018 07:47:06 PM CET - 31374: handle_request: request received (Version = 2) from PID 31504 Fri 19 Jan 2018 07:47:06 PM CET - 31374: GETFDGR  


×