Kein Zugriff auf Plesk :8443

D

dejv

New Member
Hallo,

ich kann mich seit 4 Tagen nicht anmelden, kann auf port 8443 nicht zugreifen. Plesk 8.2.1, Suse9.3, Strato V-Server
Habe das von mehreren Rechnern ausprobiert, Plesk mit "/etc/init.d/psa start" gestartet, /etc/init.d/psa status is running
port :80 geht auch nicht
Strato habe ich schon 2 e-mails geschrieben aber die antworten nicht, schon 4 Tage! :confused:
Zum letzten mal habe ich noch einen zweiten Kunden erstellt mit einer Domain und dann noch daran noch 1 Tag gearbeitet und seitdem gehts nicht :(
Ftp und alle Domains laufen wie immer
Default server seite ohne 8443 ergibt, "hosting for this domain is not configured", das ist normal?

Hat jmd vieleicht eine Idee was ich noch ausprobieren kann?

Vielen Dank!

Gruß,
David
 
Last edited by a moderator:
Hm, mach mal nen
Code: 
netstat -alnp | grep 8443
und poste die Ausgabe.
Sicherheitshalber vorher noch mittels
Code: 
/etc/init.d/psa restart
Plesk neu starten. Sollte der grep Befehl keine Ausgabe liefern, geht irgendwas schief!

Dann schau einfach mal in /var/log/messages (als erste Anlaufstelle).

--marneus

P.S. Strato muss auch nicht antworten, weil das in Deinem Verantwortungsbereich liegt.
 
marneus said:
Hm, mach mal nen
Code: 
netstat -alnp | grep 8443
P.S. Strato muss auch nicht antworten, weil das in Deinem Verantwortungsbereich liegt.
Click to expand...

Ich finde, es gehört wenigstens dazu einen Ansatz zu geben oder eben zu schreiben dass der Fehler nicht in ihrem Bereich liegt.
Ich habe vor 10 Tagen auch ein Ticket wegen meinen Fehlerhaften Balken in den Stats geschrieben, keine Antwort.
Ich glaub die sch... sich alle die Hose voll, aus Angst von UnitedInternet aufgekauft zu werden.
 
Hallo,

blaich said:
Ich glaub die sch... sich alle die Hose voll, aus Angst von UnitedInternet aufgekauft zu werden.
Click to expand...

Was ein Blödsinn.

Die machen genau das richtige.

Denn wie Marneus schon schrieb ist das sein Problem und nicht das Problem von Strato.
Also warum sollte Strato auf solche Mails reagieren.
 
Hallo,

Code: 
netstat -alnp | grep 8443

Hat ausgegeben:

Code: 
netstat -alnp | grep 8443
tcp        0      0 0.0.0.0:8443            0.0.0.0:*               LISTEN      21509/httpsd

Sicherheitshalber vorher noch mittels
Code: 
/etc/init.d/psa restart
Plesk neu starten. Sollte der grep Befehl keine Ausgabe liefern, geht irgendwas schief!

Vielen dank marneus, jetzt gehts wieder! :rolleyes:

Code: 
Dann schau einfach mal in /var/log/messages (als erste Anlaufstelle).

hat ausgegeben:
Code: 
-bash: /var/log/messages: Keine Berechtigung

P.S. Strato muss auch nicht antworten, weil das in Deinem Verantwortungsbereich liegt.
Click to expand...
Also das habe ich nicht gewußt, danke!

Gruß,
David
 
Dann lief Plesk aus irgendeinem Grunde nicht korrekt oder gar nicht.

Logfiles schaut man sich unter Linux mittels
Code: 
less /var/log/messages
an. Gibt noch weitere Befehle: cat, more, tail, head uvm.

Arbeite Dich besser in die Materie ein, dann können wir bei Fehlern auch besser helfen.

--marneus
 
Danke marneus!

Strato hat erst heute geantwortet
Code: 
less /var/log/messages
Dec 13 11:39:04 hxxxxxxx syslogd 1.4.1: restart.
Dec 13 11:39:04 hxxxxxxx sshd[28421]: Invalid user lashonn from 72.4.161.181
Dec 13 11:39:04 hxxxxxxx syslogd 1.4.1: restart.
Dec 13 11:39:05 hxxxxxxx sshd[28436]: Invalid user last from 72.4.161.181
Dec 13 11:39:06 hxxxxxxx sshd[28458]: Invalid user laszlo from 72.4.161.181
Dec 13 11:39:07 hxxxxxxx sshd[28461]: Invalid user latafat from 72.4.161.181
Dec 13 11:39:09 hxxxxxxx sshd[28463]: Invalid user lataijah from 72.4.161.181
Dec 13 11:39:10 hxxxxxxx sshd[28465]: Invalid user lateasha from 72.4.161.181
Dec 13 11:39:11 hxxxxxxx sshd[28467]: Invalid user laterrica from 72.4.161.181
Dec 13 11:39:12 hxxxxxxx sshd[28469]: Invalid user latia from 72.4.161.181
Dec 13 11:39:14 hxxxxxxx sshd[28471]: Invalid user latiana from 72.4.161.181
Dec 13 11:39:15 hxxxxxxx sshd[28473]: Invalid user latifidale from 72.4.161.181
Dec 13 11:39:16 hxxxxxxx sshd[28480]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:17 hxxxxxxx sshd[28482]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:18 hxxxxxxx sshd[28484]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:20 hxxxxxxx sshd[28486]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:21 hxxxxxxx sshd[28489]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:22 hxxxxxxx sshd[28491]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:23 hxxxxxxx sshd[28493]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:25 hxxxxxxx sshd[28495]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:26 hxxxxxxx sshd[28497]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:27 hxxxxxxx sshd[28499]: Invalid user latitia from 72.4.161.181
Dec 13 11:39:28 hxxxxxxx sshd[28501]: Invalid user latoya from 72.4.161.181
...
.
...
Dec 13 11:44:59 hxxxxxxx sshd[31845]: Invalid user lez from 72.4.161.181
Dec 13 11:45:00 hxxxxxxx sshd[31849]: Invalid user lfhagel from 72.4.161.181
Dec 13 11:45:01 hxxxxxxx sshd[31873]: Invalid user lgarcia from 72.4.161.181
Dec 13 11:45:01 hxxxxxxx /usr/sbin/cron[31902]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 13 11:45:02 hxxxxxxx sshd[31934]: Invalid user lgasataya from 72.4.161.181
Dec 13 11:45:04 hxxxxxxx sshd[31941]: Invalid user lgrunwald from 72.4.161.181
...
...
...
Dec 14 04:22:29 hxxxxxxx proftpd[20438]: hxxxxxxx.stratoserver.net (85.181.117.3
4[85.181.117.34]) - mod_delay/0.5: delaying for 22501 usecs
Dec 14 04:30:01 hxxxxxxx /usr/sbin/cron[22236]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 14 04:31:27 hxxxxxxx proftpd[20438]: hxxxxxxx.stratoserver.net (85.181.117.3
4[85.181.117.34]) - PAM(setcred): Memory buffer error
Dec 14 04:31:27 hxxxxxxx proftpd[20438]: hxxxxxxx.stratoserver.net (85.181.117.3
4[85.181.117.34]) - PAM(close_session): Memory buffer error
...
...
...
Dec 14 07:38:17 hxxxxxxx sshd[23947]: Invalid user Jarmo from 72.4.161.181
Dec 14 07:38:19 hxxxxxxx sshd[23949]: Invalid user Jarno from 72.4.161.181
Dec 14 07:38:20 hxxxxxxx sshd[23953]: Invalid user Jenni from 72.4.161.181
Dec 14 07:38:21 hxxxxxxx sshd[23955]: Invalid user Jere from 72.4.161.181
Dec 14 07:38:22 hxxxxxxx sshd[23966]: Invalid user Jeremias from 72.4.161.181
Dec 14 07:38:24 hxxxxxxx sshd[23970]: Invalid user Joel from 72.4.161.181
Dec 14 07:38:25 hxxxxxxx sshd[23972]: Invalid user Johanna from 72.4.161.181
Dec 14 07:38:26 hxxxxxxx sshd[23974]: Invalid user Johannes from 72.4.161.181
Dec 14 07:38:27 hxxxxxxx sshd[23978]: Invalid user Joni from 72.4.161.181
Dec 14 07:38:29 hxxxxxxx sshd[23980]: Invalid user Jonna from 72.4.161.181
..
...
...
Dec 14 08:38:34 hxxxxxxx sshd[11270]: Invalid user admin from 24.25.63.187
Dec 14 08:38:48 hxxxxxxx sshd[11275]: Invalid user stud from 24.25.63.187
Dec 14 08:38:53 hxxxxxxx sshd[11278]: Invalid user trash from 24.25.63.187
Dec 14 08:39:01 hxxxxxxx sshd[11280]: Invalid user aaron from 24.25.63.187
Dec 14 08:39:11 hxxxxxxx sshd[11301]: Invalid user gt05 from 24.25.63.187
...
...
...
KIN ATTEMPT!
Dec 14 23:22:39 hxxxxxxx sshd[23575]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:22:42 hxxxxxxx sshd[23579]: Invalid user office from 65.167.52.10
Dec 14 23:22:42 hxxxxxxx sshd[23579]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:22:44 hxxxxxxx sshd[23583]: Invalid user samba from 65.167.52.10
Dec 14 23:22:44 hxxxxxxx sshd[23583]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:22:47 hxxxxxxx sshd[23585]: Invalid user tomcat from 65.167.52.10
Dec 14 23:22:47 hxxxxxxx sshd[23585]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:22:50 hxxxxxxx sshd[23590]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:22:53 hxxxxxxx sshd[23594]: Invalid user spam from 65.167.52.10
Dec 14 23:22:53 hxxxxxxx sshd[23594]: reverse mapping checking getaddrinfo for a
dsl_corporativo16752-10.etb.net.co.52.167.65.in-addr.arpa failed - POSSIBLE BREA
KIN ATTEMPT!
Dec 14 23:30:01 hxxxxxxx /usr/sbin/cron[24406]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 14 23:40:15 hxxxxxxx -- MARK --
Dec 14 23:45:01 hxxxxxxx /usr/sbin/cron[27927]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 15 00:00:01 hxxxxxxx /usr/sbin/cron[30257]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
...
Dec 15 02:40:15 hxxxxxxx -- MARK --
Dec 15 02:45:01 hxxxxxxx /usr/sbin/cron[28046]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 15 03:00:01 hxxxxxxx /usr/sbin/cron[29861]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 15 03:15:01 hxxxxxxx /usr/sbin/cron[31962]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 15 03:30:01 hxxxxxxx /usr/sbin/cron[1839]: (root) CMD (/usr/local/psa/admin/
sbin/backupmng >/dev/null 2>&1)
Dec 15 03:40:15 hxxxxxxx -- MARK --

...
...
...
Dec 16 14:15:13 hxxxxxxx sshd[29912]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:14 hxxxxxxx sshd[29916]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:17 hxxxxxxx sshd[29938]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:18 hxxxxxxx sshd[29940]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:19 hxxxxxxx sshd[29943]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:19 hxxxxxxx sshd[29959]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:20 hxxxxxxx sshd[29961]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:21 hxxxxxxx sshd[29972]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:25 hxxxxxxx sshd[29981]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:25 hxxxxxxx sshd[29985]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:26 hxxxxxxx sshd[29994]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
...
...
Dec 16 14:15:50 hxxxxxxx sshd[30099]: Invalid user admin from 195.190.124.210
Dec 16 14:15:50 hxxxxxxx sshd[30099]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:50 hxxxxxxx sshd[30102]: Invalid user admin from 195.190.124.210
Dec 16 14:15:50 hxxxxxxx sshd[30102]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:51 hxxxxxxx sshd[30107]: Invalid user admin from 195.190.124.210
Dec 16 14:15:51 hxxxxxxx sshd[30107]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:51 hxxxxxxx sshd[30124]: Invalid user admin from 195.190.124.210
Dec 16 14:15:51 hxxxxxxx sshd[30124]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:15:52 hxxxxxxx sshd[30126]: Invalid user admin1 from 195.190.124.210
Dec 16 14:15:52 hxxxxxxx sshd[30126]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
...
...
Dec 16 14:17:19 hxxxxxxx sshd[31762]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:17:19 hxxxxxxx sshd[31764]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:17:20 hxxxxxxx sshd[31770]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:17:20 hxxxxxxx sshd[31782]: Invalid user nagios from 195.190.124.210
Dec 16 14:17:20 hxxxxxxx sshd[31782]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
Dec 16 14:17:21 hxxxxxxx sshd[31787]: Invalid user nagios from 195.190.124.210
Dec 16 14:17:21 hxxxxxxx sshd[31787]: reverse mapping checking getaddrinfo for 2
10.kirovtelecom.ru failed - POSSIBLE BREAKIN ATTEMPT!
...
...
Dec 17 02:15:01 hxxxxxxx /usr/sbin/cron[15844]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 17 02:30:01 hxxxxxxx /usr/sbin/cron[17568]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 17 02:37:10 hxxxxxxx sshd[19499]: Invalid user admin from 72.4.161.181
Dec 17 02:37:12 hxxxxxxx sshd[19503]: Invalid user admin from 72.4.161.181
Dec 17 02:37:13 hxxxxxxx sshd[19507]: Invalid user admin from 72.4.161.181
Dec 17 02:37:14 hxxxxxxx sshd[19511]: Invalid user admin from 72.4.161.181
Dec 17 02:37:16 hxxxxxxx sshd[19517]: Invalid user admin from 72.4.161.181
Dec 17 02:37:17 hxxxxxxx sshd[19523]: Invalid user admin from 72.4.161.181
Dec 17 02:45:01 hxxxxxxx /usr/sbin/cron[20008]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
Dec 17 03:00:01 hxxxxxxx /usr/sbin/cron[21719]: (root) CMD (/usr/local/psa/admin
/sbin/backupmng >/dev/null 2>&1)
...
...
...
Dec 17 10:59:30 hxxxxxxx sshd[20101]: Invalid user admin2 from 72.4.161.181
Dec 17 10:59:32 hxxxxxxx sshd[20105]: Invalid user admin from 72.4.161.181
Dec 17 10:59:33 hxxxxxxx sshd[20109]: Invalid user admin from 72.4.161.181
Dec 17 10:59:34 hxxxxxxx sshd[20113]: Invalid user admin from 72.4.161.181
Dec 17 10:59:36 hxxxxxxx sshd[20117]: Invalid user admin from 72.4.161.181
Dec 17 10:59:37 hxxxxxxx sshd[20121]: Invalid user admin from 72.4.161.181

------------------------------------
Das sieht nicht gut aus oder? :(

Gruß,
David
 
Last edited by a moderator:
Das ist ganz gewöhnliches "Hintergrundrauschen" auf Port 22. Solange deine Passwörter sicher genug gesetzt sind, bzw. der SSH Login nur per Key erlaubt ist, würd ich mir keine Sorgen machen ;). Am besten ein Tool wie Denyhosts installieren und/oder den SSH Port verlegen.
 
You must log in or register to reply here.
Back
Top