Can't Access CP

[Scroller]

anyone having problem accessing CP? I'm on NT10. Can't seem to login. what's wrong again?

yes, I'm can't access cp and can't access site on nt9.

[admin]

CP seems fine to me.. We are already looking in to NT9.

[Scroller]

both these are down for me ...

http://r4270.res.hsphere.cc:8080/pso...oft.hsphere.CP
https://cp.hsphere.cc:8443/psoft/ser...oft.hsphere.CP

[Scroller]

just came back up ... but significantly slow.

[admin]

I think psoft is doing some thing in the CP but seems ok now...

NT9 was our fault.. Its fixed for good now.. We installed a new mail server for H-SPhere and some one used the IP of NT9.. Not me but some one is getting an a$$ kicking today..

[BCS]

Was the NT9 issue also involving errors in the end user CP display for disk space? Control panel was showing:

not available/not available MB

Never saw that one before

[admin]

Right now when a NT server goes down and you have an NT account it can really slow down the CP and turn the diskusage to read.

We hope this will be fixed in 2.3 as i told the owner of Psoft about this problem..

On the unix side it does not mess with the CP as much when the web server goes down.

Admin, what have you heard about an updated release date for 2.3? It was supposed to be Monday this week, correct? And then postponed for a security fix? They released the fix for OpenSSL vulnerability earlier this week. Was that the one they were waiting for? I've been watching the boards over there too and haven't seen anything. Do you have any inside info?

[admin]

Not yet.. I just emailed them to find out.. They seem to be a little behind after having to fix that hole..

[jammin]

Originally posted by admin
I think psoft is doing some thing in the CP but seems ok now...

NT9 was our fault.. Its fixed for good now.. We installed a new mail server for H-SPhere and some one used the IP of NT9.. Not me but some one is getting an a$$ kicking today..

Could this also be why I had some weird mail problems (mails intermittently bouncing with "invalid recipient") ? Maybe they were going to the wrong mail server ?