My.VPSLink.com Support | Forum profile

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?

We should have this issue resolved per yesterday's private message conversation - OK to close thread?

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.

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.

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.

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.

my.vpslink.com is up on my end (I just logged in successfully). Try again?

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 ...

I was missing a trailing . in my A record's name field: Code: earthsgone.com. A 67.223.236.28 14400 ------------ --^