Титла: Проблем с достъпа на сайта?
Публикувано от: heminei в Jul 31, 2010, 18:58
Аз мога да си влизам в сайта, но никой друг не може. Това е конфиг файла: <VirtualHost *:80> ServerAdmin webmaster@localhost
DocumentRoot /media/Disk_F/site <Directory /> Options FollowSymLinks AllowOverride none Order allow,deny allow from all </Directory> <Directory /media/Disk_F/site> Options Indexes FollowSymLinks MultiViews AllowOverride none Order allow,deny allow from all </Directory>
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ <Directory "/usr/lib/cgi-bin"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all </Directory>
ErrorLog /var/log/apache2/error.log
# Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn
CustomLog /var/log/apache2/access.log combined
Alias /doc/ "/usr/share/doc/" <Directory "/usr/share/doc/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 </Directory>
</VirtualHost> Казвайте идеи от какво може да е, и как да го оправя. ;)
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: b2l в Jul 31, 2010, 19:12
Звездите нищо не казват. cat /etc/apache2/apache2.conf cat /etc/apache2/ports.conf cat /etc/hosts ls -la /var/www ifconfig -a route -a И още доста такива работи.
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: heminei в Jul 31, 2010, 19:21
cat /etc/apache2/apache2.conf # # Based upon the NCSA server configuration files originally by Rob McCool. # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See http://httpd.apache.org/docs/2.2/ for detailed information about # the directives. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections: # 1. Directives that control the operation of the Apache server process as a # whole (the 'global environment'). # 2. Directives that define the parameters of the 'main' or 'default' server, # which responds to requests that aren't handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "/var/log/apache2/foo.log" # with ServerRoot set to "" will be interpreted by the # server as "//var/log/apache2/foo.log". #
### Section 1: Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. #
# # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation (available # at <URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile>); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/etc/apache2"
# # The accept serialization lock file MUST BE STORED ON A LOCAL DISK. # #<IfModule !mpm_winnt.c> #<IfModule !mpm_netware.c> LockFile /var/lock/apache2/accept.lock #</IfModule> #</IfModule>
# # PidFile: The file in which the server should record its process # identification number when it starts. # This needs to be set in /etc/apache2/envvars # PidFile ${APACHE_PID_FILE}
# # Timeout: The number of seconds before receives and sends time out. # Timeout 300
# # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive On
# # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100
# # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15
## ## Server-Pool Size Regulation (MPM specific) ##
# prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_prefork_module> StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 </IfModule>
# worker MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_worker_module> StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0 </IfModule>
# event MPM # StartServers: initial number of server processes to start # MaxClients: maximum number of simultaneous client connections # MinSpareThreads: minimum number of worker threads which are kept spare # MaxSpareThreads: maximum number of worker threads which are kept spare # ThreadsPerChild: constant number of worker threads in each server process # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule mpm_event_module> StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxRequestsPerChild 0 </IfModule>
# These need to be set in /etc/apache2/envvars User ${APACHE_RUN_USER} Group ${APACHE_RUN_GROUP}
# # AccessFileName: The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. #
AccessFileName .htaccess
# # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <Files ~ "^\.ht"> Order allow,deny Deny from all Satisfy all </Files>
# # DefaultType is the default MIME type the server will use for a document # if it cannot otherwise determine one, such as from filename extensions. # If your server contains mostly text or HTML documents, "text/plain" is # a good value. If most of your content is binary, such as applications # or images, you may want to use "application/octet-stream" instead to # keep browsers from trying to display binary files as though they are # text. # DefaultType text/plain
# # HostnameLookups: Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it'd be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # HostnameLookups Off
# ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog /var/log/apache2/error.log
# # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn
# Include module configuration: Include /etc/apache2/mods-enabled/*.load Include /etc/apache2/mods-enabled/*.conf
# Include all the user configurations: Include /etc/apache2/httpd.conf
# Include ports listing Include /etc/apache2/ports.conf
# # The following directives define some format nicknames for use with # a CustomLog directive (see below). # If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i # LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %O" common LogFormat "%{Referer}i -> %U" referer LogFormat "%{User-agent}i" agent
# # Define an access log for VirtualHosts that don't define their own logfile CustomLog /var/log/apache2/other_vhosts_access.log vhost_combined
# Include of directories ignores editors' and dpkg's backup files, # see README.Debian for details.
# Include generic snippets of statements Include /etc/apache2/conf.d/
# Include the virtual host configurations: Include /etc/apache2/sites-enabled/ cat /etc/apache2/ports.conf # If you just change the port or add more ports here, you will likely also # have to change the VirtualHost statement in # /etc/apache2/sites-enabled/000-default # This is also true if you have upgraded from before 2.2.9-3 (i.e. from # Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and # README.Debian.gz
NameVirtualHost *:80 Listen 80
<IfModule mod_ssl.c> # If you add NameVirtualHost *:443 here, you will also have to change # the VirtualHost statement in /etc/apache2/sites-available/default-ssl # to <VirtualHost *:443> # Server Name Indication for SSL named virtual hosts is currently not # supported by MSIE on Windows XP. Listen 443 </IfModule>
<IfModule mod_gnutls.c> Listen 443 </IfModule>
cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 heminei-desktop
# The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts ls -la /var/www общо 16 drwxr-xr-x 2 root root 4096 2010-07-30 21:17 . drwxr-xr-x 16 root root 4096 2010-07-29 12:43 .. -rw-r--r-- 1 root root 177 2010-07-29 12:44 index.html lrwxrwxrwx 1 root root 22 2010-07-30 11:35 phpmyadmin -> /usr/share/phpmyadmin/ lrwxrwxrwx 1 root root 13 2010-07-30 21:16 site -> /Disk_F/site/ lrwxrwxrwx 1 root root 19 2010-07-30 21:17 sitee -> /media/Disk_F/site/ -rw-r--r-- 1 root root 21 2010-07-30 11:35 test.php
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: b2l в Jul 31, 2010, 19:27
ЕЙ тука: GeSHi (HTML): <VirtualHost *:80>
Ако си сложиш IP-то не знам какво ще стане??? (вместо *-ката)
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: heminei в Jul 31, 2010, 19:40
Нестава! Други идеи??
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: nigl в Jul 31, 2010, 21:05
cat /etc/hosts
Код:
127.0.0.1 localhost 127.0.1.1 heminei-desktop
======================== 127.0.0.1 localhost.localdomain localhost ip-to FQDN
на първо четене
и нещо не ти е коректен апача-нямаш отворен порт/за тези от подписа/
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: morbid_viper в Jul 31, 2010, 23:52
като гледам апача е настроен както би трябвало да се настрои за да поддържа виртуални домейни, като изключим липсата на клаузата „ServerName <твоя домейн>“, която обикновено е точно след ServerAdmin. без нея ти ще си я отваряш, защото знаеш, че е на това ip, но комшията няма как да знае. предполагам, че това ти е и единствен виртуален домейн на този апач и затова ти отваря него по подразбиране. ако все пак искаш да добавиш повече домейни към този, например „www.<твоя домейн>“ или „mushmula.<твоя домейн>“, то трябва да използваш и клаузата ServerAlias, като предварително ти трябва и съответното зареждане на модул „vhost_alias“.
Друго: * все пак провери дали имаш подходящ DNS запис, който да води към тази машина. ако си го сложиш само в /etc/hosts, то ще си го виждаш само ти – трябва да се добави към DNS записите за домейна
* също така виж дали защитната стена е разрешила достъп до 80-ти порт. ако е вътре в локална мрежа провери и дали пренасочването на порта е както трябва на машината, от която получаваш интернет.
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: jet в Aug 01, 2010, 00:17
вземи дай повече инфо: кой е този сайт дето ти влизаш, а другите не как пробваш да влезеш и как пробват те (отговор като http://localhost не се приемат) тези дето не могат да влязат в твоята мрежа ли са до тук и IP не видяхме
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: heminei в Aug 01, 2010, 00:58
Значи сайта ( http://www.heminei.com) ми е с купен домейн на който DNS му е мойто IP. Пробвах през прокси да влизам в него, и казах на мои познати да проват но не става.
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: b2l в Aug 01, 2010, 01:42
И за какво през прокси?
ПС: Btw по името на домейна ми се струва, че сайта ти е за гейове и май повече няма да пиша в тази тема.
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: n00b в Aug 01, 2010, 02:42
Машината да не е спряна? Или има пуснат firewall?
212.50.93.72?
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: heminei в Aug 01, 2010, 06:46
Никога не е спрян компютъра! @backtolife, сайта е за музика?!?
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: nigl в Aug 01, 2010, 08:54
Справка за сайта - някаква тракерформа за музика
morbid_viper даде правилно насочване. тук http://httpd.apache.org/docs/2.0/vhosts/examples.html имаш официално инфо
-------------------
сега виждам, че имаш и друга тема по въпроса. явно нещо се е омазало. дано имаш копие на базата. остави това ЛАМП и си инсталирай Апаче, Ма-скл и пхп, качи си нещата ... т.н
Титла: Re: Проблем с достъпа на сайта?
Публикувано от: heminei в Aug 01, 2010, 14:07
Оправи се! Преинсталирах линукса, и се оправи :)
|