Started 6 days, 13 hours ago (2009-11-24 16:16:00)
by GuyPatterson
Quote:
Originally Posted by jncraton
Although I'm 99% sure I had the right password, I went ahead and reset it anyway. I could not log in using the new password either. Basically, I can't log in. Any ideas?
Thanks.
Yes. Could be the byproduct of: Seattle
Datacenter Outage - 11/23/2009
Started 1 week, 4 days ago (2009-11-20 05:20:00)
by DanL@VPSLink
The last estimate I received from our template developers was "next week" (that was last week) - I'll check in again and report back as more information becomes available.
Started 2 months ago (2009-09-28 19:22:00)
by DanL@VPSLink
Your request has been fulfilled at this time - our billing department is involved in the upgrade process presently, however, our development team is tasked with invoice automation to support billing for this activity.
My understanding is that your VPS allocation should have been updated immediately when you upgraded - was this not the case?
Started 2 months, 1 week ago (2009-09-24 22:31:00)
by DanL@VPSLink
We should have this issue resolved per yesterday's private message conversation - OK to close thread?
Started 2 months, 1 week ago (2009-09-20 23:05:00)
by factorial
Turns out I had
SCP access, so I scp'd in and renamed .bash_profile to .bash_profile.ignore and now I can ssh again. Apparently screen wasn't happy with being in .bash_profile... hope this helps someone in the future.
Started 2 months, 1 week ago (2009-09-20 23:09:00)
by factorial
Have you checked your /etc/hosts.deny and /etc/hosts.allow files? Or your iptables? Perhaps you have firewall settings somewhere preventing connections at port 22. Also check your
sshd_config file (in /etc/ssh/ for me on Fedora) and make sure your ssh port is in fact 22.
Started 2 months, 1 week ago (2009-09-20 03:52:00)
by DanL@VPSLink
This is a billing issue and I do show that you have a ticket with our billing department open at this time, however, they will not be in the office for another
36 hours.
I would be happy to help in the interim - please check your PM's.
Started 2 months, 2 weeks ago (2009-09-14 19:17:00)
by DanL@VPSLink
Firstly, please accept my apologies for the delay in our response on this issue.
We should have a resolution for you momentarily - you can expect a reply to your ticket with our billing department and a service credit in accordance with our
Service Level Agreement for this inconvenience with your new line of service.
Started 4 months, 1 week ago (2009-07-21 21:43:00)
by GuyPatterson
my.vpslink.com is up on my end (I just logged in successfully).
Try again?
Started 2 months, 3 weeks ago (2009-09-07 16:15:00)
by GuyPatterson
Quote:
Originally Posted by Partner
Code:
Temporary error fetching os_template list. Please retry.$VAR1 = { 'status' => 'error', 'type' => 'protocol', 'message' => 'HTTP Code 500' };
unable to
get request ID!
Any ideas what's going on?
500 = "Internal Server Error" so VPSlink's web and/or application ...
Size: 1,025 bytes
