Bräuchte Hilfe bei der installation des GT Chats

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    Bräuchte Hilfe bei der installation des GT Chats

    Guten Tag ihr lieben,

    folgendes Problem. Wir versuchen seit 2 Tagen den GT Chat zu installieren aber bisher keinen Erfolg.
    Wenn wir auf die chat.pl verlinken kommt nur der inhalt der Datei aber der Chat wird nicht geöffnet.

    #mce_temp_url#

    Haben die settings.dat angepasst aber bisher keinen Erfolg um überhaupt in den Chat zu gelangen.
    Hat vlt einer einen Rat?
    Hi ho

    wie ich sehe ist der Chat auf der Domain im Verzeichnis chat/ hat dieser Ordner auch Perl freigegeben?
    bzw. ist auf dem Server überhaubt cgi oder Perl aktiv????

    Kann es sein das ihr bei den Anbiter seid?`contabo.de/?show=webhosting und das Webspace-Paket M habt wenn ja dann solltet ihr Updaten weil dort drin befindet sich kein cgi was der Chat aber Benötigt :thinking:

    Und wenn ick mich nicht irre dann mal schöne GRüße Indra XDDDDD
    Wenn ick mich irre dann sorry Lg xXNeoXx Ak. Panter :vain:
    Hosting-Panter.eu - Home
    Antiref.net


    if ($ahnung == 'keine' ) { use ( FAQ ) && ( Google | | Suche ) }
    if ($antwort == 0 ) { post ( Frage ) }
    Hi Neo

    ja der server hat LAMP also auch Perl
    und wir haben das Paket VPS M

    So sieht unser Perl gerade aus in der config weil bei Debian 7 heist das Ding ja apache2.conf

    # This is the main Apache server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See Apache HTTP Server Version 2.4
    Documentation - Apache HTTP Server
    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:core - Apache HTTP Server>);
    # 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., Welcome to The Apache Software Foundation! (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 number 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


    Aber mein Freund und ich kommen da einfach nicht weiter, auch wenn das Verzeichnis cgi-bin heist findet er es nicht
    Vielelicht kannst du uns weiter helfen.

    lg Hendrik und Indra
    Hi ho

    Ihr müst entweder dem Server sagen cgi Acripte ühberall ausführen oder cgi scripte nur in dem Ordner ausführen.
    Wo man dies nun genau einstellt kann ich euch leider auch nicht sagen, weil mit Server einstellungen habe selbst ich immer andere leute machen lassen.

    Habt ihr eine Oberfleche also Plask oder Parallels Confixx?? weil meist Stellt man das dort alles ein.

    vielleicht hat ja jemand anderes auch noch eine Idee bzw. kennt sich besser mit einstellen eines Servers aus...

    Lg.
    Hosting-Panter.eu - Home
    Antiref.net


    if ($ahnung == 'keine' ) { use ( FAQ ) && ( Google | | Suche ) }
    if ($antwort == 0 ) { post ( Frage ) }
    hi neo

    eine Oberfleche also Plask oder Parallels Confixx haben wir nicht. (co ich gebs zu ich kenn mich da selber nicht so top aus Neo aber hendrik sagt das).
    Schade das du da nicht weiter weist, dann müssen wir eben warten oder eine andere Lösung finden.

    Vielleicht kennt sich da doch noch einer aus.
    Auf jedenfall erst mal danke.

    Lg Indra