[Gelöst] IPV6 aktivieren und port freigeben

Begonnen von SamNitro, 24 März 2017, 14:11:04

Vorheriges Thema - Nächstes Thema

SamNitro

ich habe mir den port 8083 global gelassen darüber kann ich fhem noch erreichen.

aber port 8084 und 8085 habe ich nur lokal (so nenne ich das mal) gemacht darüber geht nix mehr.

wie rufe ich das log file auf?
(Intel-Nuc Proxmox) (Homematic) (EnOcean) (CUL868) (CUL433) (Zigbee2MQTT) (ESP8266) (Echo) (DUOFERN)

Wernieman

d.h. Du möchtest, das extern nur auf port 8083 kommt -> Funzt
und bei port 8084-85?

Die Logfiles findest Du, wie unter Linux üblich, unter /var/log ...
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

SamNitro

Zitat von: Wernieman am 30 März 2017, 17:33:56
d.h. Du möchtest, das extern nur auf port 8083 kommt -> Funzt
und bei port 8084-85?

Die Logfiles findest Du, wie unter Linux üblich, unter /var/log ...

laut der Anleitung soll ich doch alle global entfernen und dann nur noch über proxy auf port 8084... aber die Weiterleitung klappt noch nicht. im access.log bekomme ich bei jedem zugriff die Meldung:

192.168.1.133 - - [30/Mar/2017:18:16:15 +0200] "GET /fhem HTTP/1.1" 404 500 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8"




das hier ist der error.log
[Thu Mar 30 16:05:51.917397 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:05:51.922495 2017] [core:notice] [pid 14247:tid 3069448720] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:18:12.587857 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 30 16:18:12.903117 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:18:12.903305 2017] [core:notice] [pid 14247:tid 3069448720] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:18:17.861371 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 30 16:18:18.180996 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:18:18.181197 2017] [core:notice] [pid 14247:tid 3069448720] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:22:57.199281 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00493: SIGUSR1 received.  Doing graceful restart
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
[Thu Mar 30 16:22:57.496728 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:22:57.497019 2017] [core:notice] [pid 14247:tid 3069448720] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:23:03.172237 2017] [mpm_event:notice] [pid 14247:tid 3069448720] AH00491: caught SIGTERM, shutting down
[Thu Mar 30 16:23:05.492238 2017] [mpm_event:notice] [pid 15484:tid 3069379088] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:23:05.493483 2017] [core:notice] [pid 15484:tid 3069379088] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:25:20.168354 2017] [mpm_event:notice] [pid 15484:tid 3069379088] AH00491: caught SIGTERM, shutting down
[Thu Mar 30 16:25:43.307053 2017] [mpm_event:notice] [pid 651:tid 3070120464] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:25:43.314909 2017] [core:notice] [pid 651:tid 3070120464] AH00094: Command line: '/usr/sbin/apache2'
[Thu Mar 30 16:33:37.307895 2017] [mpm_event:notice] [pid 651:tid 3070120464] AH00491: caught SIGTERM, shutting down
[Thu Mar 30 16:34:00.286372 2017] [mpm_event:notice] [pid 648:tid 3069579792] AH00489: Apache/2.4.10 (Raspbian) configured -- resuming normal operations
[Thu Mar 30 16:34:00.324350 2017] [core:notice] [pid 648:tid 3069579792] AH00094: Command line: '/usr/sbin/apache2'
(Intel-Nuc Proxmox) (Homematic) (EnOcean) (CUL868) (CUL433) (Zigbee2MQTT) (ESP8266) (Echo) (DUOFERN)

Wernieman

Gib mir bitte mal Deine apache-config ...
und ein netstat -lntp
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

SamNitro

netstat -lntp
(No info could be read for "-p": geteuid()=1000 but you should be root.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:8083            0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:8084          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:8085          0.0.0.0:*               LISTEN      -               
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -               
tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      -               
tcp        0      0 0.0.0.0:8383            0.0.0.0:*               LISTEN      -               
tcp        0      0 0.0.0.0:7072            0.0.0.0:*               LISTEN      -               
tcp6       0      0 :::80                   :::*                    LISTEN      -               
tcp6       0      0 :::22                   :::*                    LISTEN      -               
tcp6       0      0 :::1883                 :::*                    LISTEN      -               

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


hoffe das ist die config
(Intel-Nuc Proxmox) (Homematic) (EnOcean) (CUL868) (CUL433) (Zigbee2MQTT) (ESP8266) (Echo) (DUOFERN)

Wernieman

Dad ist die "Globalconfig". Irgendwo hast Du doch den proxy für den Apache eingetragen. Guck mal in

IncludeOptional conf-enabled/*.conf
IncludeOptional sites-enabled/*.conf
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html

SamNitro

#51
mittlerweile habe ich die fhem.conf von dem hier:
<Location /fhem>
  # ProxyPass/ProxyPassReverse leitet HTTP requests auf eine andere URL um
  ProxyPass http://localhost:8084/fhem
  ProxyPassReverse http://localhost:8084/fhem
  ProxyHTMLEnable On
  # ProxyHTMLURLMap passt Links im HTML/JavaScript Source an
  ProxyHTMLURLMap /        /fhem/
  ProxyHTMLURLMap /fhem/     /fhem/
  AuthType Basic
  AuthName &quot;Password Required&quot;
  AuthUserFile /etc/fhem-htpasswd
  Require valid-user
  Order deny,allow
  Allow from all
</Location>

auf das reduziert uns so läuft es:
<IfModule mod_proxy.c>
  <Location /fhem>
    ProxyPass http://localhost:8084/fhem
    ProxyPassReverse http://localhost:8084/fhem
  </Location>
</IfModule>


aber jetzt ohne passwort abfrage
wenn ich die mit rein nehme funktioniert nicht einmal der Neustart des apache, habe gelesen da hat sich was bei der version 2.4 geändert. aber was genau jetzt in die config muss keine Ahnung.


Edit:

Jetzt läuft es:

Die fhem.conf sieht jetzt so aus:
<IfModule mod_proxy.c>
  <Location /fhem>
    ProxyPass http://localhost:8084/fhem
    ProxyPassReverse http://localhost:8084/fhem
    AuthType Basic
    AuthName "Authentication Required"
    AuthUserFile "/etc/fhem-htpasswd"
    Require valid-user
    Order allow,deny
    Allow from all
  </Location>
</IfModule>



Hatte basicauth bei fhem noch an....
(Intel-Nuc Proxmox) (Homematic) (EnOcean) (CUL868) (CUL433) (Zigbee2MQTT) (ESP8266) (Echo) (DUOFERN)

Wernieman

Nur für die Lesbarkeit, würde folgendes an den Anfang des Blockes schreiben:
   Order allow,deny
    Allow from all

So ist es praktisch  Standard
- Bitte um Input für Output
- When there is a Shell, there is a Way
- Wann war Dein letztes Backup?

Wie man Fragen stellt: https://tty1.net/smart-questions_de.html