Page 1 of 2 | 1 | 2 | > | >> | All |
Posted By: kyme32 on October 25, 2013, 1:42 am | Post: 1 |
now i saw my spelling mistake(sorry eng it's not my primary lang)
when i added the subdomain both domain and sub went to noindexpage or what ever is that, title says "Default Website Page" and i have a index.php on root /public_html/index.php on my domain and /public_html/subdomain/index.php for subdomain is there any problem with ftp or there are uploaded to another path? i noticed that nameservers are restarting by them selfs to default and primary ip => my lan ip(strange thing) error log for my domain Quote [Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'tokenizer' already loaded in Unknown on line 0
[Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'pdo_sqlite' already loaded in Unknown on line 0 [Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'iconv' already loaded in Unknown on line 0 [Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'ctype' already loaded in Unknown on line 0 [Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'SQLite' already loaded in Unknown on line 0 [Fri Oct 25 07:13:39 2013] [error] [client 188.215.77.17] PHP Warning: Module 'PDO' already loaded in Unknown on line 0 repeating alot subdomain log it's clean and webserver log it's huge Quote httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName
httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName [Fri Oct 25 07:41:28 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sessqwfmd5f6yhzng3gn/index.php?act=domainmanage [Fri Oct 25 07:39:37 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:39:35 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sessqwfmd5f6yhzng3gn/index.php?act=domainmanage [Fri Oct 25 07:35:52 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sessqwfmd5f6yhzng3gn/index.php?act=domainmanage [Fri Oct 25 07:35:42 2013] [notice] mod_ruid2/0.9.4 enabled [Fri Oct 25 07:35:42 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 07:35:42 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 07:35:14 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:25:36 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:25:35 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:16:25 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:16:25 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:16:20 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:16:19 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:41 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:40 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:39 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:39 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:38 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:32 2013] [notice] mod_ruid2/0.9.4 enabled [Fri Oct 25 07:15:32 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 07:15:32 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 07:15:23 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:20 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:18 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sesstuxpxbs8va8c0yuv/index.php?act=domainmanage [Fri Oct 25 07:15:17 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:16 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 07:15:14 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sesstuxpxbs8va8c0yuv/index.php?act=domainmanage [Fri Oct 25 07:15:13 2013] [error] [client 188.215.77.17] File does not exist: /usr/local/apps/apache/www/favicon.ico [Fri Oct 25 07:15:13 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sesstuxpxbs8va8c0yuv/index.php?act=domainmanage [Fri Oct 25 07:14:39 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/, referer: http://192.168.0.2:2002/sesstuxpxbs8va8c0yuv/index.php?act=domainmanage [Fri Oct 25 07:14:31 2013] [notice] mod_ruid2/0.9.4 enabled [Fri Oct 25 07:14:31 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 07:14:31 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 07:02:24 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 07:02:24 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 07:00:26 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 07:00:26 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 06:57:10 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 06:56:01 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations |
Posted By: valley on October 25, 2013, 6:18 am | Post: 2 |
Quote i installed centos, from 0, i installed webuzo, everything worked fine beside that when i entred the details of my account and doman and all licence i wait like 1h and nothing, so i tried the login and it seems to work all fine so i don't worry about it Sir Webuzo downloads and install the LAMP package at the initial setup and depending on your Internet connection it will take time. Had you installed Webuzo issuing the following command: Code Root > ./install.sh --install=none The initial setup would have been faster and you could further install the LAMP Stack from your Webuzo Enduser Panel using the following guide: http://www.webuzo.com/wiki/Install_System_Apps Note : Leaving the Initial Setup undone, leaves the Webuzo machine configured in a semi-crashed state. Quote i have installed the dns manager first of all and before the sub all worked good, now i get only noindex page Check whether the Services are running. You can follow this guide: http://webuzo.com/wiki/Restart_services Quote under install configuration i don't have the nameservers inputs so i fill them up in namservers under admin like so Sir you manually installed Webuzo, you should have the nameserver fields. You can download the ready-to-cook VM from the Webuzo Downloads Page http://webuzo.com/downloads Quote if you need more details or anything please let me know, and i forgot to say, i'm behind a firewall(simple dlink router with dmz pointing to server and port fw done Aah!!! It's probably the Firewall causing the trouble. Make sure it is routed properly. Quote when i added the subdomain both domain and sub went to noindexpage or what ever is that, title says "Default Website Page" and i have a index.php on root Restart the Webuzo Service: Code Root > service webuzo restart Restart the Apache Webserver: Code Root > service httpd restart Alternately, try to re-install(remove and install) the Webserver from the Webuzo Enduser Panel. Guide : http://www.webuzo.com/wiki/Install_System_Apps Quote is there any problem with ftp or there are uploaded to another path? Assuming you have uploaded the files to the right path. You can confirm the path to your Domains and FTP Paths using this guide: Guide : http://www.webuzo.com/wiki/Manage_Domain Guide : http://www.webuzo.com/wiki/Manage_FTP Quote i noticed that nameservers are restarting by them selfs to default and primary ip => my lan ip(strange thing) What is the IP you inputted the Admin Nameserver Settings ? That's used in the Apache Configuration. Quote and webserver log it's huge Well Sir, a webserver re-install is recommended. You can use the tutorial share above. Hope it helps !!! ----------------------- Webuzo : Single User Control Panel Join Webuzo : |
Posted By: kyme32 on October 25, 2013, 8:00 am | Post: 3 |
now i tried it again
install centos with "localhost" on hostname if that matters installed wget and fully update the centos and rebooted wget -N http://files.webuzo.com/install.sh chmod 0755 install.sh ./install.sh --install=none all was fine, install compeleted and now time for setup via browser i've noticed that when i copy the link from putty and go to it it redirect me to my lan ip on web install i got username email password repassword primary domain(with my lan ip under) and licence key, no nameservers at all i filled them up and in 20sec for my surprize was done, other times i waited like 15 30min and still was loading that circle now under admin :2004 port under settings/nameservers i putted like this my external ip address(it was prefilled with my lan ip) domain was ok, and ns1 ns2 changed to my domains ns now user settings :2002 port, installed apache, pureftpd, mysql, bind, php 5.4 and rebooted to make sure that all works as it should created a ftp user with root in /home/soft/www uploaded in root of ftp an index.php and i get "Default Website Page" i tried with .html too but same result, i also coment everything in /usr/local/apps/apache/etc/conf.d/welcome.conf and when i access the domain now i get Forbidden You don't have permission to access / on this server. any ideas how can i fix this sir? the log seems quite full even after a fresh install for like 10 times domain log it's clean and here's the webserver log httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName httpd: Could not reliably determine the server's fully qualified domain name, using ::1 for ServerName [Fri Oct 25 13:55:58 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:50 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:50 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:48 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:53:46 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 13:53:46 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 13:49:00 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:59 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:57 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 13:48:57 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 13:48:55 2013] [notice] child pid 3257 exit signal Segmentation fault (11) [Fri Oct 25 13:48:55 2013] [notice] child pid 3256 exit signal Segmentation fault (11) [Fri Oct 25 13:48:55 2013] [notice] child pid 3255 exit signal Segmentation fault (11) [Fri Oct 25 13:48:55 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:54 2013] [notice] child pid 3254 exit signal Segmentation fault (11) [Fri Oct 25 13:48:54 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:54 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:53 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:48:52 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 13:48:52 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 13:45:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:49 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:48 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:47 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:46 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:45:45 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:40:37 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:40:35 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:40:35 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:40:34 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:39:33 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:39:25 2013] [notice] SIGHUP received. Attempting to restart [Fri Oct 25 13:39:25 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 13:38:52 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:38:38 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:38:37 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:38:33 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:34:19 2013] [error] [client 5.10.83.57] File does not exist: /usr/local/apps/apache/www/functional-slider.html [Fri Oct 25 13:28:21 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:28:20 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:28:19 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:28:18 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:28:17 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:26:37 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations [Fri Oct 25 13:26:16 2013] [notice] caught SIGTERM, shutting down [Fri Oct 25 13:25:52 2013] [error] [client 188.215.77.17] Directory index forbidden by Options directive: /usr/local/apps/apache/www/ [Fri Oct 25 13:24:01 2013] [notice] Apache/2.2.24 (Unix) DAV/2 mod_ssl/2.2.24 OpenSSL/1.0.1e configured -- resuming normal operations |
Posted By: kyme32 on October 25, 2013, 8:18 am | Post: 4 |
here are the ports open. nameserver settings on register company and on the webuzo interface and the bind settings if that helps
https://www.dropbox.com/sh/mic9go8s6ksxv8m/vb71JuuiRk#/ |
Posted By: valley on October 25, 2013, 11:37 am | Post: 5 |
Quote i've noticed that when i copy the link from putty and go to it it redirect me to my lan ip Well Sir, do not use that link in case of a VM deployed manually. Fetch the IP of the machine using the following command and access http://IP:2002 for the Webuzo Enduser Panel Code Root > ifconfig Quote i filled them up and in 20sec for my surprize was done, other times i waited like 15 30min and still was loading that circle Aah !!! That's because you chose --install=none initially. Quote now under admin :2004 port under settings/nameservers i putted like this my external ip address(it was prefilled with my lan ip) domain was ok, and ns1 ns2 changed to my domains ns Put you machine IP as the Primary IP and not the LAN IP. Rest of the settings look fine. Quote now user settings :2002 port, installed apache, pureftpd, mysql, bind, php 5.4 and rebooted to make sure that all works as it should Well a reboot wasn't actually necessary. Simply restart the services from the terminal of from the Webuzo Enduser Panel itself Quote created a ftp user with root in /home/soft/www uploaded in root of ftp an index.php and i get "Default Website Page" i tried with .html Once you have followed the above step - to change the Primary IP , you will be able to access the page. Correct me if I am wrong. Quote too but same result, i also coment everything in /usr/local/apps/apache/etc/conf.d/welcome.conf and when i access the domain now i get Forbidden You don't have permission to access / on this server. You need not do this. It is recommended you do not alter the Webuzo configurations. Quote any ideas how can i fix this sir? Try changing the Primary IP to the Machine IP as discussed above to be able to fix your issues. Once the above changes are done, access you site using you IP directly rather than your domain to confirm the working. Hope it helps. Good Luck ----------------------- Webuzo : Single User Control Panel Join Webuzo : |
Posted By: kyme32 on October 26, 2013, 2:33 am | Post: 9 |
Quote From : codesight October 25, 2013, 12:50 pm Quote Try changing the Primary IP to the Machine IP as discussed above to be able to fix your issues. Exactly!! Don't change anything besides that. Changing the Ip from internal to external causes exactly this behavior. Revert ist and u should be fine. i am using external ip for the primary ip, are you suggesting to use internal ip? external=188.215.77.17 internal=192.168.0.2 Quote Did you set port forwarding für UDP+TCP 53? Is your Webuzo allowed to send traffic to any external?
Your webuzo server goes all the way out to external and back zu internal zu resolv some names. yes i did sir, it's pressent for both udp+tpc 53 under name "Virtual Server DNS" under pics from dropbox what i post i've changed the primary ip to my lan ip(machine ip it's lan ip)and now everything works as it should BUT, it's not visible to others, works only for me(tested via proxy online) or maybe somebody from here can confirm that http://kyme32.ro should say "kyme32.ro page" later i'm gonna ask one of my friends to give me his mac address to put my wmware bridged with my internet due the mac auth i can't do that right now, my internet provider use macs to validate login, now my wmware it's bridged with my actual router and manually set to 192.168.0.2 as a internal ip, this ip i used for primary ip, the same ip from ifconfig eth0 i have a old switch and when i get that mac i would use it to connect both(pc and wmware)to internet provider network and have 2 different external ip's and reinstall the whole thing one small fast question, what should i use under installing centos as hostname? if i use kyme32.ro(my primary domain) it will be fine?or it may cause problems(better usei localhost)? or "localhost.kyme32.ro"? honestly i don't understand how this should work if i use my local ip for primary ip, on my point of view that ip access every user on my domain, it's like if they have an apache on 192.168.0.2 on there lan they will see they server on my domain(kinda if you get what i mean, maybe not, i don't know, it's something beyond my knowledge) it may be only due propagation my new ip but can anybody please tell me if they can access http://kyme32.ro or http://ytinst.kyme32.ro? thank you |
Posted By: codesight on October 26, 2013, 9:20 am | Post: 10 |
[quote poster=kyme32 date=1382754805]
i've changed the primary ip to my lan ip(machine ip it's lan ip)and now everything works as it should BUT, it's not visible to others, works only for me(tested via proxy online) or maybe somebody from here can confirm that http://kyme32.ro should say "kyme32.ro page" later i'm gonna ask one of my friends to give me his mac address to put my wmware bridged with my internet due the mac auth i can't do that right now, my internet provider use macs to validate login, now my wmware it's bridged with my actual router and manually set to 192.168.0.2 as a internal ip, this ip i used for primary ip, the same ip from ifconfig eth0 i have a old switch and when i get that mac i would use it to connect both(pc and wmware)to internet provider network and have 2 different external ip's and reinstall the whole thing[/quote] honestly, try to play by punctuation rules and use passages - cause I don't understand a thing u try to say. [quote poster=kyme32 date=1382754805] one small fast question, what should i use under installing centos as hostname? if i use kyme32.ro(my primary domain) it will be fine?or it may cause problems(better usei localhost)? or "localhost.kyme32.ro"?[/quote] Localhost ist a very bad idea, since this is pre-defined. kyme32.ro is no hostname, it is a domain-name. host.kyme32.ro would be a hostname. U need to read some stuff about DNS and FQDN! [quote poster=kyme32 date=1382754805] honestly i don't understand how this should work if i use my local ip for primary ip, on my point of view that ip access every user on my domain, it's like if they have an apache on 192.168.0.2 on there lan they will see they server on my domain(kinda if you get what i mean, maybe not, i don't know, it's something beyond my knowledge) it may be only due propagation my new ip but[/quote] Of course, no one can access your webserver if you don't route and foward ports. You need to tell your firewall to send every package coming in on external:80 send to internal:80 - Port 443 similar. Do you have an Knowledge in networking, routing and Port-fowarding? If not, then I'd suggest you cut the idea about a routing firewall and put your webserver straight into the internet and try to secure it on itsself. Or you start learning a lot of stuff very very fast. [/quote] ----------------------- Don't you dare to ask for root details! |
Posted By: codesight on October 26, 2013, 9:21 am | Post: 11 |
Quote From : kyme32 October 26, 2013, 2:33 am i've changed the primary ip to my lan ip(machine ip it's lan ip)and now everything works as it should BUT, it's not visible to others, works only for me(tested via proxy online) or maybe somebody from here can confirm that http://kyme32.ro should say "kyme32.ro page" later i'm gonna ask one of my friends to give me his mac address to put my wmware bridged with my internet due the mac auth i can't do that right now, my internet provider use macs to validate login, now my wmware it's bridged with my actual router and manually set to 192.168.0.2 as a internal ip, this ip i used for primary ip, the same ip from ifconfig eth0 i have a old switch and when i get that mac i would use it to connect both(pc and wmware)to internet provider network and have 2 different external ip's and reinstall the whole thing honestly, try to play by punctuation rules and use passages - cause I don't understand a thing u try to say. Quote From : kyme32 October 26, 2013, 2:33 am one small fast question, what should i use under installing centos as hostname? if i use kyme32.ro(my primary domain) it will be fine?or it may cause problems(better usei localhost)? or "localhost.kyme32.ro"? Localhost ist a very bad idea, since this is pre-defined. kyme32.ro is no hostname, it is a domain-name. host.kyme32.ro would be a hostname. U need to read some stuff about DNS and FQDN! Quote From : kyme32 October 26, 2013, 2:33 am honestly i don't understand how this should work if i use my local ip for primary ip, on my point of view that ip access every user on my domain, it's like if they have an apache on 192.168.0.2 on there lan they will see they server on my domain(kinda if you get what i mean, maybe not, i don't know, it's something beyond my knowledge) it may be only due propagation my new ip but Of course, no one can access your webserver if you don't route and foward ports. You need to tell your firewall to send every package coming in on external:80 send to internal:80 - Port 443 similar. Do you have an Knowledge in networking, routing and Port-fowarding? If not, then I'd suggest you cut the idea about a routing firewall and put your webserver straight into the internet and try to secure it on itsself. Or you start learning a lot of stuff very very fast. ----------------------- Don't you dare to ask for root details! |
Posted By: kyme32 on October 26, 2013, 9:35 am | Post: 12 |
Quote From : codesight October 26, 2013, 9:21 am Quote From : kyme32 October 26, 2013, 2:33 am i've changed the primary ip to my lan ip(machine ip it's lan ip)and now everything works as it should BUT, it's not visible to others, works only for me(tested via proxy online) or maybe somebody from here can confirm that http://kyme32.ro should say "kyme32.ro page" later i'm gonna ask one of my friends to give me his mac address to put my wmware bridged with my internet due the mac auth i can't do that right now, my internet provider use macs to validate login, now my wmware it's bridged with my actual router and manually set to 192.168.0.2 as a internal ip, this ip i used for primary ip, the same ip from ifconfig eth0 i have a old switch and when i get that mac i would use it to connect both(pc and wmware)to internet provider network and have 2 different external ip's and reinstall the whole thing honestly, try to play by punctuation rules and use passages - cause I don't understand a thing u try to say. Quote From : kyme32 October 26, 2013, 2:33 am one small fast question, what should i use under installing centos as hostname? if i use kyme32.ro(my primary domain) it will be fine?or it may cause problems(better usei localhost)? or "localhost.kyme32.ro"? Localhost ist a very bad idea, since this is pre-defined. kyme32.ro is no hostname, it is a domain-name. host.kyme32.ro would be a hostname. U need to read some stuff about DNS and FQDN! Quote From : kyme32 October 26, 2013, 2:33 am honestly i don't understand how this should work if i use my local ip for primary ip, on my point of view that ip access every user on my domain, it's like if they have an apache on 192.168.0.2 on there lan they will see they server on my domain(kinda if you get what i mean, maybe not, i don't know, it's something beyond my knowledge) it may be only due propagation my new ip but Of course, no one can access your webserver if you don't route and foward ports. You need to tell your firewall to send every package coming in on external:80 send to internal:80 - Port 443 similar. Do you have an Knowledge in networking, routing and Port-fowarding? If not, then I'd suggest you cut the idea about a routing firewall and put your webserver straight into the internet and try to secure it on itsself. Or you start learning a lot of stuff very very fast. sorry about my crazy writing, i understood that with port fw and i did it, i hosted webserver on my main pc under windows ~2y with cnames pointing to my ip and all was fine, now i try to do a fancy* stuff and try under linux and see how it works. now i'm installing everything from scratch underi a switch to have under my laptop external ip and no internal or router involved. hopefully this gonna work as i expect. i will let you now guys after i finish the install thank you |
Posted By: codesight on October 26, 2013, 9:39 am | Post: 13 |
Use fail2ban at least to secure your linux server, after you've set it up.
----------------------- Don't you dare to ask for root details! |
Posted By: valley on October 28, 2013, 5:51 am | Post: 15 |
Quote From : kyme32 October 27, 2013, 11:10 pm it took me ~3h to install mysql on it, and i'm sure it's not from my internet connection, i have 95mbit/90mbit(down/up) connection. under wmware works as oiled, if you know somehow guys some fix for this issue i will be glad to try it. Sir the MySQL package weighs ~60MB and is downloaded only once as long as there is no update available. I doubt you will face this issue again. Quote once again thank you for support guys, i guess i would buy this product, it's simply awesome, i love it Thanks for the appreciation. Please do spread the word. Thanks to @codesight as well Quote From : kyme32 October 27, 2013, 11:10 pm one small question about licenses, what license i would need to buy? webuzo license include softaculous?(alots of scripts to install) and differences between dedicated server and vps?on a dedicated server license you can hold more vps's?am i right? for example i would buy webuzo for vps, that will be exactly the same as it's right now in trial license? thank you As long as your IP remains static, you can purchase the VPS Server License. OR you can opt for the Virtual Appliance and Cloud License (for internal use only) Webuzo comes with built-in Softaculous and hence you have the benefit of deploying over 310+ scripts by a click. Once you purchase the license for Webuzo, it will be the same as in the Trial License. Edited by valley : October 28, 2013, 5:52 am ----------------------- Webuzo : Single User Control Panel Join Webuzo : |