Página da pasta do apache não carrega em rede local [RESOLVIDO]

Mr.Robot
(usa Ubuntu)

Enviado em 21/04/2016 - 12:07h

Olá, pessoal.
Estou com um Desktop Ubuntu com apache2 ativado e phpmyadmin. Dentro do próprio Ubuntu consigo ver minha pagina pelo ip interno(192.168.254.1) pelo 'localhost' e pelo 127.0.0.1 no navegador mas em outro computador da mesma rede local boto o ip e não abre a página. O Nmap diz que a porta '80/tcp http' está aberta. O que falta?
Detalhe, pelo Ubuntu consigo acessar a página de outro computador na mesma rede. Isso me leva a presumir que há alguma configuração no Ubuntu que esteja impedindo o acesso. Mas não achei nada pesquisando.

msoliver
(usa Debian)

Enviado em 21/04/2016 - 15:43h

Boa tarde Robot.
Veja o arquivo de configuração do apache: "httpd.conf"
Especificamente as linhas:
Deny from all
Allow from 127.0.0.1

você está negando para todos e liberando apenas pro lookback.
Troque
Deny from all
Por:
Allow from All

Salve e restarte o apache.

E não esqueça....
Se resolver, marque como RESOLVIDO.
Se a minha RESPOSTA te AJUDOU, marque a como a MELHOR, assim ganho pontos,
o que incentiva a continuar ajudando . . . :)

Abç.:
Marcelo Oliver

Mr.Robot
(usa Ubuntu)

Enviado em 21/04/2016 - 17:24h

Procurei por esse arquivo e só existe um chamado 'lighttpd.conf' na pasta do phpmyadmin e não tem nada parecido com essas linhas. Fucei toda pasta do Apache e o mais parecido com o que você citou (e algum tutos) que encontrei foi isso:

apache2/conf-available/security.conf

#<Directory />

#   AllowOverride None

#   Order Deny,Allow

#   Deny from all

#</Directory>

 

Não sei em que linguagem isso ta escrito mas parece que o '#' transforma os códigos em comentário e a mudança de Deny para Allow não tem efeito.
Será que essas #'s foram acrescentados pela instalação do phpmyadmin?

Mr.Robot
(usa Ubuntu)

Enviado em 21/04/2016 - 21:49h

Reinstalei tudo: apache2, php5, mysql e phpmyadmin.
Segui essa instalação, link do youtube : /watch?v=2e9a3azeogY
Agora o arquivo apache2.conf veio maior e com as configurações que eu procurava:

# 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.4/ for detailed information about

# the directives and /usr/share/doc/apache2/README.Debian about Debian specific

# hints.

#

#

# Summary of how the Apache 2 configuration works in Debian:

# The Apache 2 web server configuration in Debian is quite different to

# upstream's suggested way to configure the web server. This is because Debian's

# default Apache2 installation attempts to make adding and removing modules,

# virtual hosts, and extra configuration directives as flexible as possible, in

# order to make automating the changes and administering the server as easy as

# possible.



# It is split into several files forming the configuration hierarchy outlined

# below, all located in the /etc/apache2/ directory:

#

#	/etc/apache2/

#	|-- apache2.conf

#	|	`--  ports.conf

#	|-- mods-enabled

#	|	|-- *.load

#	|	`-- *.conf

#	|-- conf-enabled

#	|	`-- *.conf

# 	`-- sites-enabled

#	 	`-- *.conf

#

#

# * apache2.conf is the main configuration file (this file). It puts the pieces

#   together by including all remaining configuration files when starting up the

#   web server.

#

# * ports.conf is always included from the main configuration file. It is

#   supposed to determine listening ports for incoming connections which can be

#   customized anytime.

#

# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/

#   directories contain particular configuration snippets which manage modules,

#   global configuration fragments, or virtual host configurations,

#   respectively.

#

#   They are activated by symlinking available configuration files from their

#   respective *-available/ counterparts. These should be managed by using our

#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See

#   their respective man pages for detailed information.

#

# * The binary is called apache2. Due to the use of environment variables, in

#   the default configuration, apache2 needs to be started/stopped with

#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not

#   work with the default configuration.





# Global configuration

#



#

# 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 Mutex documentation (available

# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);

# 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.

#

Mutex file:${APACHE_LOCK_DIR} default



#

# 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 5





# These need to be set in /etc/apache2/envvars

User ${APACHE_RUN_USER}

Group ${APACHE_RUN_GROUP}



#

# 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 ${APACHE_LOG_DIR}/error.log



#

# LogLevel: Control the severity of messages logged to the error_log.

# Available values: trace8, ..., trace1, debug, info, notice, warn,

# error, crit, alert, emerg.

# It is also possible to configure the log level for particular modules, e.g.

# "LogLevel info ssl:warn"

#

LogLevel warn



# Include module configuration:

IncludeOptional mods-enabled/*.load

IncludeOptional mods-enabled/*.conf



# Include list of ports to listen on

Include ports.conf





# Sets the default security model of the Apache2 HTTPD server. It does

# not allow access to the root filesystem outside of /usr/share and /var/www.

# The former is used by web applications packaged in Debian,

# the latter may be used for local directories served by the web server. If

# your system is serving content from a sub-directory in /srv you must allow

# access here, or in any related virtual host.

<Directory />

	Options FollowSymLinks

	AllowOverride None

#	Require all denied

	Require all granted

</Directory>



<Directory /usr/share>

	AllowOverride None

	Require all granted

</Directory>



<Directory /var/www/>

	Options Indexes FollowSymLinks

	AllowOverride None

	Require all granted

</Directory>



#<Directory /srv/>

#	Options Indexes FollowSymLinks

#	AllowOverride None

#	Require all granted

#</Directory>









# 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.

#

<FilesMatch "^\.ht">

#	Require all denied

	Require all granted

</FilesMatch>





#

# The following directives define some format nicknames for use with

# a CustomLog directive.

#

# These deviate from the Common Log Format definitions in that they use %O

# (the actual bytes sent including headers) instead of %b (the size of the

# requested file), because the latter makes it impossible to detect partial

# requests.

#

# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.

# Use mod_remoteip instead.

#

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



# Include of directories ignores editors' and dpkg's backup files,

# see README.Debian for details.



# Include generic snippets of statements

IncludeOptional conf-enabled/*.conf



# Include the virtual host configurations:

IncludeOptional sites-enabled/*.conf



# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

 

Fiz as mudanças em destaque, mas ainda sem sucesso.

leosixers
(usa Debian)

Enviado em 22/04/2016 - 16:08h

Qual é o erro exibido no navegador quando você tenta acessar de outra máquina na rede?

Mr.Robot
(usa Ubuntu)

Enviado em 22/04/2016 - 18:33h

O navegador fica carregando até atingir o tempo limite.
Agora me parece que o problema são as permissões do Ubuntu, pois até para eu mesmo poder escrever minhas paginas na pasta /var/www/html tive que usar:

chmod 777 -R 'pasta' 

mas não sei quais pastas e que forma é melhor para mudar as permissões.

leosixers
(usa Debian)

Enviado em 25/04/2016 - 07:42h

Você não deveria usar chmod 777 jamais. Apenas em momentos de debug mesmo para verificar se é um erro de permissão.Verifique qual é o usuário que está executando o apache (ps -ef ) e de as permissões necessárias para ele.

Normalmente:

chown -R apache: /var/www/html
chmod -R 755 /var/www/html

Se você consegue acessar da máquina local o erro não deve estar relacionado a permissão.

De outra máquina da rede digite o seguinte comando:

telnet IP_do_APACHE 80

e verifique se a conexão é estabelecida.

Abraços

Mr.Robot
(usa Ubuntu)

Enviado em 27/04/2016 - 09:58h

A solução era mais simples que eu imaginava, descobri que o firewall do computador estava bloqueando o acesso. Bastou adicionar uma regra no no firewall que dá acesso á porta 80 que consegui acessar. Obrigado ajuda de vcs.
Viva o linux!