OTRS 5 - Error during AJAX communication
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
OTRS 5 - Error during AJAX communication
Guten Morgen zusammen,
seit dem Update auf OTRS 5 erhalte ich nun vermehrt AJAX Error-Meldungen.
Error during AJAX communication. Status: error, Error: Forbidden
OTRS + Apache Log sagen dazu nichts.
seit dem Update auf OTRS 5 erhalte ich nun vermehrt AJAX Error-Meldungen.
Error during AJAX communication. Status: error, Error: Forbidden
OTRS + Apache Log sagen dazu nichts.
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: OTRS 5 - Error during AJAX communication
Dann bleibt nur noch die Java-Konsole des Browsers
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Eintrag im Apache2 Log gefunden
Code: Select all
[Mon Oct 26 08:52:45 2015] [error] [client 81.xxx29] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://xxx/otrs/index.pl?Action=AgentTicketAttachment;Subaction=HTMLView;ArticleID=24$
ERROR: OTRS-CGI-30 Perl: 5.14.2 OS: linux Time: Mon Oct 26 08:53:05 2015
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Ich habe nun mal die neue /opt/otrs/scripts/apache2-httpd.include.conf genommen. Vielleicht hat sich das Problem dadurch behoben - werde berichten
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Also problem tritt weiterhin auf.
Zusammenfassung für euch:
Debian 7
Apache 2.2
MySQL 5.x
Check.Modules OK
Auf dem System läuft ausschließlich das OTRS-System.
sites-enabled/000-default
sites-enabled/default-ssl
conf.d/otrs.conf
Apache-Log
Zusammenfassung für euch:
Debian 7
Apache 2.2
MySQL 5.x
Check.Modules OK
Auf dem System läuft ausschließlich das OTRS-System.
sites-enabled/000-default
Code: Select all
<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/>
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 ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
# Das folgende erzwingt SSL
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</VirtualHost>
Code: Select all
IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin webmaster@localhost
Servername xxx:443
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/>
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 ${APACHE_LOG_DIR}/error.log
Code: Select all
Standarddatei aus dem Source-Ordner von OTRS 5.0.1
Code: Select all
[Wed Nov 04 10:07:12 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentTicketZoom;TicketID=35538
[Wed Nov 04 10:15:19 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
[Wed Nov 04 10:27:42 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentTicketAttachment;Subaction=HTMLView;ArticleID=2$
[Wed Nov 04 10:55:46 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
[Wed Nov 4 10:57:04 2015] -e: Use of uninitialized value in substitution iterator at /opt/otrs//Kernel/System/TemplateGenerator.pm line 1099.
[Wed Nov 04 10:57:20 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
[Wed Nov 04 11:11:22 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
[Wed Nov 04 11:17:02 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentTicketAttachment;Subaction=HTMLView;ArticleID=$
[Wed Nov 04 11:19:30 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
[Wed Nov 04 11:21:30 2015] [error] [client xxx] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXX/otrs/index.pl?Action=AgentDashboard
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: OTRS 5 - Error during AJAX communication
Hast du mal versucht die otrs.conf nach conf-available/ und con-enabled to verschieben - statt nach conf.d / ?
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
diese Ordner habe ich gar nicht erst
/etc/apache2# ls
apache2.conf envvars mods-available otrs-cert sites-available
conf.d magic mods-enabled ports.conf sites-enabled
/etc/apache2# ls
apache2.conf envvars mods-available otrs-cert sites-available
conf.d magic mods-enabled ports.conf sites-enabled
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Habe nun etwas rumprobiert und auch die Permissions (bin/otrs.SetPermissions.pl --web-group=www-data) nochmal durchlaufen lassen. Kein Erfolg.
Chrome Console sagt:
Chrome Console sagt:
POST https://XXXX/otrs/index.pl 403 (Forbidden)
k.cors.a.crossDomain.send @ CommonJS_d59fb1d656837f9fb61a229e03f0eba1.js:1
n.extend.ajax @ CommonJS_d59fb1d656837f9fb61a229e03f0eba1.js:1
Core.AJAX.TargetNS.FunctionCall @ CommonJS_d59fb1d656837f9fb61a229e03f0eba1.js:1204
(anonymous function) @ ModuleJS_03558fb5569efefbb65d96b9f43f83d9.js:71
CommonJS_d59fb1d656837f9fb61a229e03f0eba1.js:1071
[ERROR] CommunicationError: Error during AJAX communication. Status: error, Error: Forbidden
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
Re: OTRS 5 - Error during AJAX communication
kopiere oder verlinke die Datei mal in /etc/apache2/sites-enabled
und starte anschießend den Apache neu...
Es mag auch ne gute Idee sein, nochmals die Caches zu löschen
otrs.Console.pl Maint::Cache::Delete
otrs.Console.pl Maint::Loader::CacheDelete
otrs.Console.pl Maint::Loader::CacheGenerate
und anschließend die Berechtigungen nochmal neuzusetzen.
Ansonsten... Update mal auf den Apache 2.4
und starte anschießend den Apache neu...
Es mag auch ne gute Idee sein, nochmals die Caches zu löschen
otrs.Console.pl Maint::Cache::Delete
otrs.Console.pl Maint::Loader::CacheDelete
otrs.Console.pl Maint::Loader::CacheGenerate
und anschließend die Berechtigungen nochmal neuzusetzen.
Ansonsten... Update mal auf den Apache 2.4
My english is better than your german
"Produktiv": OTRS: 5.0.x, OTRS::ITSM 5.0.x
"Testing": OTRS 6 git
OS: Debian 8.0 (Jessie)
Apache2.4.10/MySQL 5.5.41
"Produktiv": OTRS: 5.0.x, OTRS::ITSM 5.0.x
"Testing": OTRS 6 git
OS: Debian 8.0 (Jessie)
Apache2.4.10/MySQL 5.5.41
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Habe es in sites-available kopiert, site-aktiviert, apache2 restart. Caches gelöscht und neu generiert.
Gleiches Problem
Ich hatte dies damals auch unter OTRS 3 mit Debian 7 und auch schon bei OTRS 3 mit Windows.
Apache Update ist schon eingeplant, aber das kann ja nicht das Problem hervorrufen.
Gleiches Problem
Ich hatte dies damals auch unter OTRS 3 mit Debian 7 und auch schon bei OTRS 3 mit Windows.
Apache Update ist schon eingeplant, aber das kann ja nicht das Problem hervorrufen.
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
Re: OTRS 5 - Error during AJAX communication
Hi,
ist das nur im Dashbaord?
Hast Du den Code geändert?
Was passiert, wenn Du die ZZZAuto.pm mal entfernst, also die sysconfig komplett resettest?
Ist der Fehler dann immer noch da?
Flo
ist das nur im Dashbaord?
Hast Du den Code geändert?
Was passiert, wenn Du die ZZZAuto.pm mal entfernst, also die sysconfig komplett resettest?
Ist der Fehler dann immer noch da?
Flo
OTRS 8 SILVER (Prod)
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 8 auf Debian 11 (Test)
Znuny 7.x latest version testing auf Debian 11
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Einzig manuell geändert:
TicketViewZoom.tt (dort einfach nur eine optische Anpassung!)
AgentPreferences.tt (ebenfalls einfach nur eine optische Anpassung)
Also nichts nennenwertes.
Einen reset der Config teste ich gerne die Tage auf dem Testsystem - das dauert aber :/ Ggf. noch andere Ideen?
TicketViewZoom.tt (dort einfach nur eine optische Anpassung!)
AgentPreferences.tt (ebenfalls einfach nur eine optische Anpassung)
Also nichts nennenwertes.
Einen reset der Config teste ich gerne die Tage auf dem Testsystem - das dauert aber :/ Ggf. noch andere Ideen?
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
so habe ein Upgrade auf Debian Jessie durchgeführt und dadurch auch Apache 2.4
Fehler ist nach wie vor vorhanden.
Apache Log:
Fehler ist nach wie vor vorhanden.
Apache Log:
Code: Select all
[Sat Nov 07 13:30:30.688386 2015] [evasive20:error] [pid 1019] [client xxx:62244] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXXXXX/otrs/index.pl?Action=AgentTicketAttachm$
[Sat Nov 07 13:32:38.742628 2015] [evasive20:error] [pid 1020] [client xxx:62276] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXXXXX/otrs/index.pl?Action=AgentTicketZoom;Ti$
[Sat Nov 07 13:32:46.876249 2015] [evasive20:error] [pid 1017] [client xxx:62278] client denied by server configuration: /opt/otrs/bin/cgi-bin/index.pl, referer: https://XXXXXXX/otrs/index.pl?Action=AgentTicketZoom;Ti$
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
Re: OTRS 5 - Error during AJAX communication
zeig mal deine komplette apache config
My english is better than your german
"Produktiv": OTRS: 5.0.x, OTRS::ITSM 5.0.x
"Testing": OTRS 6 git
OS: Debian 8.0 (Jessie)
Apache2.4.10/MySQL 5.5.41
"Produktiv": OTRS: 5.0.x, OTRS::ITSM 5.0.x
"Testing": OTRS 6 git
OS: Debian 8.0 (Jessie)
Apache2.4.10/MySQL 5.5.41
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
apache2.conf
sites-enabled/default-ssl.conf
sites-enabled/000-default.conf
sites-enabled/otrs.conf
Code: Select all
# 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
Code: Select all
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin webmaster@localhost
Servername XXXX:443
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/>
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 ${APACHE_LOG_DIR}/error.log
# SSL
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
# SSL Engine Switch:
# Enable/Disable SSL for this virtual host.
SSLEngine on
# A self-signed (snakeoil) certificate can be created by installing
# the ssl-cert package. See
# /usr/share/doc/apache2.2-common/README.Debian.gz for more info.
# If both key and certificate are stored in the same file, only the
# SSLCertificateFile directive is needed.
SSLCertificateFile /etc/apache2/otrs-cert/otrs.crt
SSLCertificateKeyFile /etc/apache2/otrs-cert/otrs.key
# Server Certificate Chain:
# Point SSLCertificateChainFile at a file containing the
# concatenation of PEM encoded CA certificates which form the
# certificate chain for the server certificate. Alternatively
# the referenced file can be the same as SSLCertificateFile
# when the CA certificates are directly appended to the server
# certificate for convinience.
#SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
# Certificate Authority (CA):
# Set the CA certificate verification path where to find CA
# certificates for client authentication or alternatively one
# huge file containing all of them (file must be PEM encoded)
# Note: Inside SSLCACertificatePath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCACertificatePath /etc/ssl/certs/
#SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
# Certificate Revocation Lists (CRL):
# Set the CA revocation path where to find CA CRLs for client
# authentication or alternatively one huge file containing all
# of them (file must be PEM encoded)
# Note: Inside SSLCARevocationPath you need hash symlinks
# to point to the certificate files. Use the provided
# Makefile to update the hash symlinks after changes.
#SSLCARevocationPath /etc/apache2/ssl.crl/
#SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
# Client Authentication (Type):
# Client certificate verification type and depth. Types are
# none, optional, require and optional_no_ca. Depth is a
# number which specifies how deeply to verify the certificate
# issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth 10
# Access Control:
# With SSLRequire you can do per-directory access control based
# on arbitrary complex boolean expressions containing server
# variable checks and other lookup directives. The syntax is a
# mixture between C and Perl. See the mod_ssl documentation
# for more details.
#<Location />
#SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
# and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
# and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
# and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
# and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \
# or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>
# SSL Engine Options:
# Set various options for the SSL engine.
# o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation. This means that
# the standard Auth/DBMAuth methods can be used for access control. The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the user
# file needs this password: `xxj31ZMTZzkVA'.
# o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
# o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction step is an expensive operation and is usually
# useless for serving static content. So one usually enables the
# exportation for CGI and SSI requests only.
# o StrictRequire:
# This denies access when "SSLRequireSSL" or "SSLRequire" applied even
# under a "Satisfy any" situation, i.e. when it applies access is denied
# and no other module can change it.
# o OptRenegotiate:
# This enables optimized SSL connection renegotiation handling when SSL
# directives are used in per-directory context.
#SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
<FilesMatch "\.(cgi|shtml|phtml|php)$">
SSLOptions +StdEnvVars
</FilesMatch>
<Directory /usr/lib/cgi-bin>
SSLOptions +StdEnvVars
</Directory>
# SSL Protocol Adjustments:
# The safe and default but still SSL/TLS standard compliant shutdown
# approach is that mod_ssl sends the close notify alert but doesn't wait for
# the close notify alert from client. When you need a different shutdown
# approach you can use one of the following variables:
# o ssl-unclean-shutdown:
# This forces an unclean shutdown when the connection is closed, i.e. no
# SSL close notify alert is send or allowed to received. This violates
# the SSL/TLS standard but is needed for some brain-dead browsers. Use
# this when you receive I/O errors because of the standard approach where
# mod_ssl sends the close notify alert.
# o ssl-accurate-shutdown:
# This forces an accurate shutdown when the connection is closed, i.e. a
# SSL close notify alert is send and mod_ssl waits for the close notify
# alert of the client. This is 100% SSL/TLS standard compliant, but in
# practice often causes hanging connections with brain-dead browsers. Use
# this only for browsers where you know that their SSL implementation
# works correctly.
# Notice: Most problems of broken clients are also related to the HTTP
# keep-alive facility, so you usually additionally want to disable
# keep-alive for those clients, too. Use variable "nokeepalive" for this.
# Similarly, one has to force some clients to use HTTP/1.0 to workaround
# their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
# "force-response-1.0" for this.
BrowserMatch "MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
SSLProtocol All -SSLv2 -SSLv3
SSLHonorCipherOrder On
</VirtualHost>
</IfModule>
Code: Select all
<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory /var/www/>
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 ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
# Das folgende erzwingt SSL
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</VirtualHost>
Code: Select all
# --
# added for OTRS (http://otrs.org/)
# --
ScriptAlias /otrs/ "/opt/otrs/bin/cgi-bin/"
Alias /otrs-web/ "/opt/otrs/var/httpd/htdocs/"
<IfModule mod_perl.c>
# Setup environment and preload modules
Perlrequire /opt/otrs/scripts/apache2-perl-startup.pl
# Reload Perl modules when changed on disk
PerlModule Apache2::Reload
PerlInitHandler Apache2::Reload
# general mod_perl2 options
<Location /otrs>
# ErrorDocument 403 /otrs/customer.pl
ErrorDocument 403 /otrs/index.pl
SetHandler perl-script
PerlResponseHandler ModPerl::Registry
Options +ExecCGI
PerlOptions +ParseHeaders
PerlOptions +SetupEnv
Order allow,deny
Allow from all
<IfModule mod_version.c>
<IfVersion < 2.4>
Order allow,deny
Allow from all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
</IfModule>
<IfModule !mod_version.c>
Order allow,deny
Allow from all
</IfModule>
</Location>
# mod_perl2 options for GenericInterface
<Location /otrs/nph-genericinterface.pl>
PerlOptions -ParseHeaders
</Location>
</IfModule>
<Directory "/opt/otrs/bin/cgi-bin/">
AllowOverride None
Options +ExecCGI -Includes
<IfModule mod_version.c>
<IfVersion < 2.4>
Order allow,deny
Allow from all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
</IfModule>
<IfModule !mod_version.c>
Order allow,deny
Allow from all
</IfModule>
<IfModule mod_filter.c>
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/javascript application/javascript text/css text/xml application/json text/json
</IfModule>
</IfModule>
</Directory>
<Directory "/opt/otrs/var/httpd/htdocs/">
AllowOverride None
<IfModule mod_version.c>
<IfVersion < 2.4>
Order allow,deny
Allow from all
</IfVersion>
<IfVersion >= 2.4>
Require all granted
</IfVersion>
</IfModule>
<IfModule !mod_version.c>
Order allow,deny
Allow from all
</IfModule>
<IfModule mod_filter.c>
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/javascript application/javascript text/css text/xml application/json text/json
</IfModule>
</IfModule>
# Make sure CSS and JS files are read as UTF8 by the browsers.
AddCharset UTF-8 .css
AddCharset UTF-8 .js
# Set explicit mime type for woff fonts since it is relatively new and apache may not know about it.
AddType application/font-woff .woff
</Directory>
<IfModule mod_headers.c>
# Cache css-cache for 30 days
<Directory "/opt/otrs/var/httpd/htdocs/skins/*/*/css-cache">
<FilesMatch "\.(css|CSS)$">
Header set Cache-Control "max-age=2592000 must-revalidate"
</FilesMatch>
</Directory>
# Cache css thirdparty for 4 hours, including icon fonts
<Directory "/opt/otrs/var/httpd/htdocs/skins/*/*/css/thirdparty">
<FilesMatch "\.(css|CSS|woff|svg)$">
Header set Cache-Control "max-age=14400 must-revalidate"
</FilesMatch>
</Directory>
# Cache js-cache for 30 days
<Directory "/opt/otrs/var/httpd/htdocs/js/js-cache">
<FilesMatch "\.(js|JS)$">
Header set Cache-Control "max-age=2592000 must-revalidate"
</FilesMatch>
</Directory>
# Cache js thirdparty for 4 hours
<Directory "/opt/otrs/var/httpd/htdocs/js/thirdparty/">
<FilesMatch "\.(js|JS)$">
Header set Cache-Control "max-age=14400 must-revalidate"
</FilesMatch>
</Directory>
</IfModule>
# Limit the number of requests per child to avoid excessive memory usage
MaxRequestsPerChild 4000
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x
-
- Znuny wizard
- Posts: 554
- Joined: 25 Sep 2012, 19:04
- Znuny Version: OTRS Help Desk
- Real Name: Stefan
Re: OTRS 5 - Error during AJAX communication
Ahhh ich glaube ich habe es.
Die Feldermeldung ist eine andere im Apache-Log als am Anfang. Diese jetzt deutet auf das Modul mod_evasive hin. Die "alte" Fehlermeldung habe ich nicht mehr erhalten. Also scheint die Ursache des Hauptproblems durch das Upgrade gelöst zu sein - bis auf weiteres.
Die Feldermeldung ist eine andere im Apache-Log als am Anfang. Diese jetzt deutet auf das Modul mod_evasive hin. Die "alte" Fehlermeldung habe ich nicht mehr erhalten. Also scheint die Ursache des Hauptproblems durch das Upgrade gelöst zu sein - bis auf weiteres.
OTRS 5.x - Debian 8 - apache 2.4 - MySQL 5.x