Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Stefan1200

Pages: 1 [2] 3 4 ... 6
16
JTS3ServerMod MySQL & WebInterface / Maintenance by my web hoster
« on: September 23, 2017, 11:09:35 PM »
My web hoster is doing some maintenance work this night (CEDT). Running bots should work without problems, but if you want to start or restart the JTS3ServerMod process, it is possible that you get an error message, if the licence server is offline or if some of the used DNS servers are not updated to the new IP address of the web server.

As soon as all DNS servers are updated to the new web server IP address, everything should work again. If you have problems for more than 2 hours, please contact me by mail.

18
Until Monday evening (17th April 2017, CEST) there will be short outages of the forum and the JTS3ServerMod licence server because of maintenance work from my hoster. A running JTS3ServerMod stay online for at least 12 hours if the licence server is down, so this should not be a problem. But it is not possible to start the JTS3ServerMod process while the licence server is offline.

In case of your running JTS3ServerMod will stop, please write a mail to me with the JTS3ServerMod_InstanceManager.log file, so I can look into it.



Bis Montag Abend (17. April 2017) wird es kurze Ausfälle vom Forum und JTS3ServerMod Lizenzserver aufgrund von Wartungsarbeiten meines Hosters geben. Ein laufender JTS3ServerMod Prozess sollte für mindestens 12 Stunden online bleiben, wenn der Lizenzserver offline ist. Dies sollte also kein Problem sein. Aber der JTS3ServerMod Prozess lässt sich nicht starten, wenn der Lizenzserver offline ist.

Falls sich ein laufender JTS3ServerMod beenden sollte, schreibe mir bitte unbedingt eine E-Mail mit der JTS3ServerMod_InstanceManager.log Datei, damit ich mir das anschauen kann.

19
FAQ / How To ... / Firewall - In- and Outgoing connections
« on: January 07, 2017, 09:48:03 AM »
JTS3ServerMod - the Java program
Incoming TCP connections to the query interface port from the JTS3ServerMod web interface, which you have set at telnet_port in the JTS3ServerMod_InstanceManager.cfg.

An outgoing TCP connection to the MySQL server you have set at mysql_host and mysql_port in the JTS3ServerMod_InstanceManager.cfg.

For the licence (up to version 6.5.7) and update check (all versions):
An outgoing TCP HTTPS connection to www.stefan1200.de (default HTTPS port).

And last but not least: An outgoing TCP connection to all specified TS3 server query ports (default 10011), which you have defined at the bot settings.


JTS3ServerMod Web Interface
An outgoing TCP connection to the query interface ip and port to the JTS3ServerMod (Java program), which you have set at the Query Interface settings in the main Web Interface settings.

An outgoing TCP connection to the MySQL server you have set at the installation of the Web Interface.

An outgoing TCP connection to all specified TS3 server query ports (default 10011), which you have defined at the bot settings.

20
The web interface cache all channel and group names for up to 2 hours to speed up page loading. If you need to select a channel or group name, which was created in the last 2 hours, you can reload the cache by clicking on "Reload TS3 server data now" on the Bot Manager page, as seen on the following screenshot:
https://www.stefan1200.de/documentation/jts3servermod_mysql/webinterface3/reload_cache.png

21
-= Description =-
My Chrome browser is bugged and can't delete the download history. No matter which way you use to delete the download history, after restarting chrome, the whole download history is back.

The only solution is to delete the file "%localappdata%\Google\Chrome\User Data\Default\History", which also deletes the visited website history. For this case I created a small script, which do this.


-= Usage =-
Just unpack the download zip file and put the cmd file where you want. Double click the cmd script to delete the Chrome history.


-= Download =-
Chrome_History_Delete.zip

22
Current changelog:

Quote
Web Interface 3.0 Build 3024 (??.10.2016)
+ Admins can now delete inactive user accounts in the User Manager with less clicks, which have no bots and are not admins.
  Similar to the inactive bot deletion, introduced in build 3017.
+ New contact form, which allows users to send an email to a specified email address, without to know the email address.
  If a user is logged in, name and mail address is already in the contact form. Also a list of bots will be displayed for bot related questions.
  The recipient get a direct link to the bot settings in this case. This contact form can be disabled in the Web Interface settings.
+ It is now possible to create a new bot and copy all settings from another bot.
  Permission to create a new bot is needed (or being an admin, of course).
  Just click on the "copy bot" button in the bot list.
- Bugfix: All outgoing mails now have the right text encoding set (UTF-8), so special characters should be displayed fine in all email clients.
- Bugfix: Fixed smaller design errors.
o Added error messages to the bot user management and the web interface user management, if the bot does not exists or the admin level is to low.
o Removed more HTML code from the PHP files and put them into tmpl files.
o Changed or added files: include/userlist.php, include/register.php, include/contact.php, include/Translation.php, include/settings.php,
  include/botcreate.php, include/botlist.php, include/botmanager.php, include/botuser.php, templates/backtomain.tmpl,
  templates/botcreate.tmpl, templates/botcreate_default.tmpl, templates/botlist_all_row.tmpl, templates/botlist_row.tmpl, templates/botlist_row_copy.tmpl,
  templates/botlist_row_rename.tmpl, templates/contact.tmpl, templates/contact_email.tmpl, templates/framemenu.tmpl, templates/framemenu_user.tmpl,
  templates/settings.tmpl, templates/userlist.tmpl, templates/userlist_deleteinactiveusers.tmpl, templates/userlist_deleteinactiveusers_row.tmpl,
  index.php, sql/default.sql, sql/autoupdate/3024.sql, images/email.png, images/page_copy.png

Web Interface build 3024 is now feature complete, only bug fixing and changes because of JTS3ServerMod changes will be done.

23
General Discussions / How To: JTS3ServerMod plugin development with Eclipse
« on: September 21, 2016, 10:25:41 PM »
I created a small How To, which shows you how to setup Eclipse to create JTS3ServerMod plugins. Maybe it helps some people.

http://www.stefan1200.de/documentation/jts3servermod/jts3servermod_plugindevelopment/index.html

24
Some of you may now, that the Licence Check of the JTS3ServerMod Hosting Edition has a grace time of 12 hours, if the licence server is offline. Last night the database was not working, but the web server itself did. The server side script was not prepared for this and was sending the wrong answer to the JTS3ServerMod. That is the reason, why this grace time was not working and all your bots was stopping.

After doing a server side change, I simulated a database downtime and tested it with the JTS3ServerMod. The grace time is working now, in future a downtime with up to 12 hours of the database and/or web server will not affect a running JTS3ServerMod. Only starting a stopped JTS3ServerMod will not work while the website or database is offline.

This will give my hoster more time to fix the problems in future. No update of the JTS3ServerMod is necessary, because it was a server side fix at the licence server script.

If the licence server is not reachable, you get a message in the JTS3ServerMod_InstanceManager.log file:
LICENCE_CHECK   Error while validating heartbeat token! Reason: Licence Server answer: 500 Internal Server Error

25
Beispiel:
[^A-Za-z1-9\-\_]+

Wenn im Namen was anders vor kommt, als Buchstaben, Zahlen, Minus und Unterstrichen, wird die Funktion aktiv. Dies kann natürlich um weitere Zeichen ergänzt werden. Das Zeichen ^ ist hier aber wichtig (Negation aller Zeichen in den eckigen Klammern). Das Plus steht für beliebig viele Zeichen.

Achtung, ich habe das nicht ausgiebig getestet.

26
Since web interface build 3023 this is not needed anymore, because fatal run-time errors will be always displayed.

If you just get a white page in your browser, if you try to open the index.php or install.php of the web interface, enable the debug mode to see why this happens. By default the web interface is surpessing all PHP notices, warnings and error messages. But on critical PHP errors you see nothing.

Open the install.php and/or index.php with an editor like Notepad++, by default the first 10 lines of both files looks like:
Code: [Select]
<?PHP

error_reporting(0); ## LIVE

#ini_set('display_errors', 1); ## TESTING
#error_reporting(E_ALL);  ## TESTING


header("Content-Type: text/html; charset=utf-8");
mb_internal_encoding('UTF-8');

To enable the debug mode, comment out line 3 and uncomment the lines 5 and 6.
Code: [Select]
<?PHP

#error_reporting(0); ## LIVE

ini_set('display_errors', 1); ## TESTING
error_reporting(E_ALL);  ## TESTING


header("Content-Type: text/html; charset=utf-8");
mb_internal_encoding('UTF-8');

Save this changes to your web server. Now reload the page in your browser. Now you can read the PHP error message in your browser. After you have fixed this problem, just change both files back to the original state.

27
FAQ / How To ... / MySQL - Communications link failure
« on: July 21, 2016, 06:56:39 PM »
*** English ***
Communications link failure: This means that the DB isn't reachable at all. This can have one or more of the following causes:
  • IP address or hostname of the MySQL server in the JTS3ServerMod_InstanceManager.cfg is wrong.
  • Port number is missing or wrong of the MySQL server in the JTS3ServerMod_InstanceManager.cfg.
  • Check the bind-address attribute of the MySQL server. Make sure that the bind-address attribute in the MySQL server settings (my.cnf / my.ini) is bound to a valid network interface or "0.0.0.0".
  • Make sure, that the skip-networking attribute is disabled in the MySQL server settings (my.cnf / my.ini).
  • DB server is down.
  • DB server doesn't accept TCP/IP connections.
  • DB server has run out of connections.
  • Something in between Java and DB is blocking connections, e.g. a firewall or proxy.

This is not an error of the JTS3ServerMod, this is the error message of the Java MySQL driver or MySQL server.


*** Deutsch ***
Communications link failure: Das bedeutet, dass die Datenbank nicht erreichbar ist. Das kann eines der folgenden Gründe haben:
  • Die IP Adresse oder der Hostname vom MySQL server sind in der JTS3ServerMod_InstanceManager.cfg falsch.
  • Der Port vom MySQL Server ist in der JTS3ServerMod_InstanceManager.cfg falsch gesetzt.
  • Überprüfe das bind-address Attribut vom MySQL Server. Stelle sicher, dass das bind-address Attribut in den MySQL Server Einstellungen (my.cnf / my.ini) zu einem gültigen Netzwerk Interface oder "0.0.0.0" gebunden ist.
  • Stelle sicher, dass das skip-networking Attribut in den MySQL Server Einstellungen (my.cnf / my.ini) deaktiviert ist.
  • Datenbank Server ist offline.
  • Datenbank Server erlaubt keine TCP/IP Verbindungen.
  • Datenbank Server hat das Verbindungslimit überschritten.
  • Irgendwas zwischen Java und der Datenbank blockiert die Verbindung, z.B. eine Firewall oder Proxy.

Dies ist kein Fehler vom JTS3ServerMod, dies ist eine Fehlermeldung vom Java MySQL Treiber oder MySQL Server.

28
Die URL kann in den E-Mail Template vom Web Interface fest geändert werden, diese liegen im templates Ordner vom Web Interface. Das ist dann interessant, wenn die Personen eine andere Homepage als Einstiegsseite verwenden sollen.

Und zwar die Dateien:
newaccount_email.tmpl
pwchange_email.tmpl
register_email.tmpl
resetpw_email.tmpl

Den Eintrag {homepageurl} einfach ersetzen mit der Adresse (der Dateiname index.php muss bei der resetpw_email.tmpl mit angegeben werden), die dann in der E-Mail stehen soll. Bitte bedenken, das dies dann bei einer Änderung der Homepage Adresse (zum Beispiel bei einem Umzug) von Hand angepasst werden muss.

29
*** English ***
You get the following warning while starting the JTS3ServerMod Hosting Edition with the MySQL mode activated:
Code: [Select]
WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
This message is from the MySQL JDBC driver. Starting with the above MYSQL server versions, the MySQL connection use SSL encryption by default. You get the warning, because the MySQL server certificate can't be verified.

There are three possibilities now:
  • You get a valid certificate for your MySQL server, which can be checked by the JDBC driver (recommended, if you use a remote connection to the MySQL server).
  • You ignore the warning, so you have a encrypted connection to the MySQL server (but the remote server will not be validated).
  • You disable the SSL encryption to the MySQL server. To do this, just open the JTS3ServerMod_InstanceManager.cfg and set mysql_useSSL and mysql_verifyServerCertificate to 0 (it is okay, if you connect using localhost / 127.0.0.1 / ::1).


*** Deutsch ***
Beim Starten der JTS3ServerMod Hosting Edition mit aktiviertem MySQL Modus kommt folgende Warnung:
Code: [Select]
WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
Die Meldung kommt vom MySQL JDBC Treiber. Ab den oben genannten MySQL Server Versionen wird SSL als Standardeinstellung verwendet. Die Warnung kommt deshalb, weil das Server Zertifikat nicht verifiziert werden kann.

Man hat nun drei Möglichkeiten:
  • Du kümmerst dich um ein gültiges Zertifikat für deinen MySQL Server, das vom JDBC Treiber überprüft werden kann (empfohlen, wenn du eine Remote Verbindung zum MySQL Server aufbaust).
  • Du lebst mit den Warnungen, hast dafür aber eine verschlüsselte Verbindung zum SSL Server (bei der aber die Gegenstelle nicht überprüft werden kann).
  • Du schaltest die SSL Verschlüsselung zum MySQL Server ab. Dazu öffnest du die Datei JTS3ServerMod_InstanceManager.cfg und setzt mysql_useSSL und mysql_verifyServerCertificate auf 0 (in Ordnung, wenn du die Verbindung über localhost / 127.0.0.1 / ::1 aufbaust).

30
Offensichtlich hat mein Hoster gerade meine Daten auf einen neuen Server umgezogen, ohne mich zu informieren. Das führt dazu, das einige Sicherheitsmechanismen von der Lizenzüberprüfung aktuell anschlagen. Im Moment kann ich nur empfehlen, den Bot für die nächsten Stunden nicht neuzustarten, bis die DNS Einträge bei den externen DNS Servern aktualisiert worden sind.

Pages: 1 [2] 3 4 ... 6