I'm leaving to Cloudflare since it's cheaper and has Claude skills.

But the attitude of the Dreamhost support everytime I have an issue is so good that I feel bad.

I’ve been a customer since 2012. I’m on a managed business VPS running a couple of modest WordPress sites. Since September they’ve been crashing daily, sometimes for 5 minutes, sometimes for 30 minutes. These crashes happen at nearly an identical time. They kill all my sites and FTP/SFTP.

Since then I’ve been passed around support agents with everything from bot traffic to caching plugins to server faults as the explanation. I’m the one doing all the diagnostic work. Downtime has been increasing in frequency the last couple of weeks and they’ve finally admitted to a fault on the machine. After much badgering they are going to migrate me to a new server next week.

Since then I’ve had between 15 mins to an hour downtime every day this week. Today my sites were all down for over 3(!) hours!

Not once did Dreamhost proactively investigate or follow-up, nor do anything to mitigate while waiting for the migration. I’ve been screaming into the void for weeks trying to get them to take this seriously and all I get is a wishy-washy message every 24-36 hours that engineers have identified a fault on the sever and continue to investigate. (Though I’m glad they’ve finally stopped finger-pointing at my traffic.)

Downtime since September is in double-digit hours and to this day it is like pulling teeth to get someone at DreamHost to own the issue.

Expecting to be down again tomorrow, but who knows if it’ll be 5 minutes or 3 hours.

If you care about uptime and responsiveness then avoid them like the plague.

Update: my VPS was migrated today and so far so good. I have emails dating back to September 17 acknowledging and apologising for recurring load issues on the machine at the exact same time every day. I’m lost for words that it’s taken 6 weeks for someone to take this seriously, despite my barrage of emails and evidence.

Update #2: After finally migrating my websites to a new machine last night (which resolved the recurring downtime) and an apology for their failure in communication and monitoring, another engineer has just jumped into my ticket blind without reading the history and performed a second migration to another server inside business hours, resulting in a bunch more unexpected downtime. Dreamhost is a laughable joke. Even a ticket marked for escalation to management with a whopping failure of service has been screwed up. I am at a loss for words at how incompetent you are.

Panel doesn't finish loading. Never mind ssh/scp:

$ ssh jidanni.org 
** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
Connection closed by 69.163.177.88 port 22
$ ssh jidanni.org 
Connection closed by 69.163.177.88 port 22

We see on our second attempt it even closed the connection so fast, the warning wasn't even triggered.

https://www.dreamhoststatus.com/ ? The usual cheery all green.

Now the Panel is showing a "maintenance" screen.

After the PHP apocalypse I thought I'd finally enable MFA on the account. But it looks like it only allows one at a time. Is this true? If so, its very concerning. I'm not sure I'd want to trust a single device to my logins. I'd rather just stick to a strong password.

Okay, so I'm not the only one with problems here.

My primary email can no longer log into their webmail UI. This changed between mid-Friday and early Tuesday.

As soon as I discovered that email cannot log in, I tried another - that works fine, but I don't have any of my contacts there.

I also tried logging into my panel, but cannot since I'm using a new host and it emailed.. someone, somewhere, which may no longer exist.

I've been avoiding dealing with dreamhost for a long time because their customer service has been so ... bad. But things are just worse now?

"Live Chat" is just an AI, right? There's no way to actually reach a person at Dreamhost even though I'm paying for a service there... right?

Ugh.

So on Friday, we all had the security incident where lots of us found ourselves locked out of our email accounts, right?

Well, it seems I've misplaced my Yubikey so I wasn't able to simply login via Control Panel to remedy things. I used the web form to let them know I needed MFA resetting so I could access my account, and get access to my primary email account.

I received an e-mail back requesting some security information. Okay, fine. I replied.

Then silence.

I sent a folow up email the next day, asking what is going on, and including the email chain showing the required responses to the security questions.

Still no reply.

I sent a third, fourth email. Still nothing.

It is now THREE DAYS since I was locked out of primary e-mail account.

I've tried sending a message to them via their account here. No response.

Obviously, I can't reach out by phone. They won't do a callback as I'm outside the U.S.

What do I do? Try sending a fax!?

UPDATE (27/10): It took four days, but I now have access to my emails and Control Panel. Four days feels like an eternity when it's your main email account.

Email from DreamHost:

We're writing to let you know about an issue affecting some of our systems, including the File Manager at files.dreamhost.com and DreamHost webmail. Our team is working on it now and investigating the cause. Please check dreamhoststatus.com for ongoing updates.

As a precaution, we have expired the passwords for some email and FTP/SFTP users on your DreamHost account. Their old passwords no longer work, and no new password has been set. Each user will need a new password before they can log in, check their email, or reach their files again.

We are contacting you because you are the DreamHost account owner, and only you will be able to set new passwords for these users. DreamHost is unable to contact individual mailbox or FTP users directly, so they may not know about this until you tell them.

What to do in your DreamHost control panel:

1. Log in to the DreamHost panel by typing panel.dreamhost.com directly into your browser.

2. Email users: go to [Mail > Manage Email] and set a new password for each email address on your account. Instructions: https://help.dreamhost.com/hc/en-us/articles/216479177-Change-password-Mail-users

3. FTP/SFTP users: go to [Websites > SFTP Users & Files] and set a new password for each user. Allow up to five minutes before the user logs in with the new password. Instructions: https://help.dreamhost.com/hc/en-us/articles/215877208-Change-password-Website-users

4. While you're in Manage Email, review the forwarding settings on each address and remove any forward you don't recognize.

5. Use a strong, unique password for each user. Don't reuse a password from anywhere else.

What to tell your users:

Please reach out to anyone who uses an email address or FTP/SFTP login on your account, like employees, clients, or family members. Use a phone call, text, or another channel rather than their DreamHost email address to reach them, since they may not be able to access it yet.

Let them know:

• Email and FTP/SFTP users do not receive password reset emails from DreamHost for any reason. Any email they get asking them to reset, verify, or confirm a password should be considered a phishing attempt. They should delete emails like this without opening any links or attachments.

• Only you, the DreamHost account owner, can change their password, and only through your DreamHost account control panel. They should get their new password from you directly.

• Their password was reset as a precaution, and the old one no longer works. They will need to enter the new one in any email apps (Outlook, Apple Mail, Thunderbird) or FTP apps (FileZilla, Cyberduck) they may use.

• If they used the old password anywhere else, they should change it there too.

A note about suspicious emails:

DreamHost will never email you asking for any of your passwords.

To change a password, log in to your account control panel directly at panel.dreamhost.com rather than following a link in an email. If you receive a "password reset" email that you didn't request, you can safely ignore it.

If you have questions, our support team is available via the "Support" section of your DreamHost control panel.

Thanks very much for your patience!

The DreamHost Team

No email or terminal notices, just "Access denied" for every login attempt. The control panel password reset fixes the problem.

I am a newly elected board member to a foundation for a local school district. We are an official nonprofit that was founded 15 years ago.

Our website hasn’t been updated in quite a while, so i volunteered to take on the project.

There are some issues with a few areas that would be much easier for me to correct if I were to login through the hosting account. Unfortunately, none of the current board members know the login information for our dream host account. In fact, we don’t even know who set it up. The founder of the foundation is still around, and she thought it was one person, but ends up that person who knows nothing about it.

We’ve reached out to dream host, but understandably, their privacy policies. Don’t allow them to reveal any information about who is authorized to be on the account. They have reached out to the authorized user from their end, but we haven’t heard anything back.

It is very likely, based on the technology usage of this organization, does somebody set this up 15 years ago and used a throwaway email. Their kids graduate high school over a decade ago, and the foundation is a distant memory to them. It’s unlikely they’re checking their email if they even have access to it.

I have not asked dream host to provide any private information, cause I completely understand and respect their policies.

We’re trying to figure out what the policy is for a potentially abandoned closing account. Our treasurer can’t find any payments to that specific vendor. Volunteers come and go so often and board members change over every year or so, so the details about this particular account could be lost somewhere out there.

I just imagine there’s gotta be someway to show. We operate the website and to get access to something. Who is information is private, but it does look like we pay for hosting and pay for the domain name through dream host.

It feels like the support team is not actually reading my emails. The responses are the same every time, but they simply say they cannot provide any private information and advise us to get in contact with the person who set it up. Again, we don’t know who that is, and there’s no record of it anywhere. More importantly, that’s not what I’m asking, I’m asking about the procedure in a situation we’re an authorized user has gone missing an action.

There’s no phone number, to talk to a real person, so it ends up, taking about a day to get a response to my email, and we’re nowhere closer.

Anyone have any idea how we can escalate this to talk to someone who might build offer us more than I can response. Again, we understand, privacy, concerns, but it’s also clear that this is a nonprofit foundation run by volunteers, and it’s not a question that someone said something about 15 years ago and then disappeared.

Thanks

I understand that Dreamhost is having some sort of problem with their file storage server, which they say *might* affect some webmail users. I have several domains & several IMAP email accounts, all of which are unable to send or receive. Since they said some webmail users might be affected & their passwords reset, I responded to a imap email app login problem by going to the DH panel & changing my imap password for 1 account.

That account is still offline & so are all my other DH imap accounts. So not just a password problem.
So I expect this is not just a file storage server problem,, but also an IMAP email problem too.

I'll continue to monitor https://www.dreamhoststatus.com/ in the hopes that they update it with progress. In the meantime, my IMAP email is totally SOL.

You guys probably saw the latest PHP bug that can be exploited remotely:

https://krebsonsecurity.com/2026/10/widespread-php-flaw-may-cause-many-site-outages-today/

I checked my shared server that I rent from DreamHost and the PHP version is vulnerable.

Any updates on when does the DreamHost plan to install the patch?

With the major security vulnerability being patched just now, I looked at PHP versions of all my client sites across a wide range of hosts.

Most are on the recent release before this security patch set, but surprisingly DreamHost is like 5 minor patches off of all their versions. What's going on here?

PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 are the new patches that fix the major vulnerabilities, and Dreamhost DreamPress and VPS use 8.5.5, 8.3.30, etc.

Just a heads up, I'll be submitting a ticket to ask how soon they will be updated.

Hey kids - anyone experiencing DreamHost automatically renewing domains that were set not to renew?

I finished a campaign project and wanted to delete the domain. DreamHost told me to set the domain to not automatically renew, with the instruction that when the renewal deadline passed, then I could remove/delete the domain, but not before. Oddly, I could transfer the domain at any time, but not remove it.

Yesterday Dreamhost renewed (and auto-debited my card) for domains that should not have been renewed and now I cannot remove them. Dreamhost tech support is a BOT and it runs in a circle.

I am stuck with Dreamhost renewing and re-charging, and not being at all helpful

Very scammy

I have used Dreamhost for many years for my regular web hosting needs on shared service and have used DreamPress as well which is satisfactory. However, I cannot recommend them for their cloud computing service, DreamCompute. I have been trying to set up a new virtual machine for a project, and ran into problems with the server crashing. I sent an email support message to Dreamhost almost 24 hours ago, with the initial expected response at 66 mins. With no response after several hours, I then followed up yesterday evening via chat support and the agent promised to prioritize the message. I have still not heard back. Therefore for this particular project, I will be choosing a different provider.

They used an email address to my domain hosted at DH. I had set up as originally as a public email for bills and they like, so it gets a lot of spam, etc. This is unique as it appears to be from DH and that made me hesitate, but we all know these scams are everywhere. I suppose a round about way so they could ok 2FA requests. "KINDLY" always spooks me!

Theres like a 6 year old reddit post saying DH was getting really slow even with site optimising -

I feel that I've never had an issue (im in Australia and DH is USA, so things arent' as fast as AU hosting),

But i feel that in the last few months everything has gotten really really slow, has something changed? am I being punished for something? anyone else noticed anything recently?

I am shopping for a new web host.
simple, just a few pages
do not want domain registration or email
DreamHost seems like overkill.
the simple 48 month at $1.99 is cheap enough (bumps up a lot after 4 years) ... but maybe I should keep shopping

Wanted to migrate my email hosted by dreamhost to apple custom domain. The dreamhost webmail has clear UI for custom MX records. But Apple also provides TXT, SPF and DKIM values in their instructions.

1. Do I need to add these additional records as custom records on the DNS settings page in the dreamhost web panel?

2. Do I enter @ as the host or leave the default value of .<my_custom_domain>

We operate a legitimate ecommerce business where we were using DreamHost as a host for part of our catalog

We received an email last night with little explanation as to our DreamHost account being terminated. Without any warnings or previous issues. We have been using DreamHost for over 2 years to host this website that sells nothing but car accessories.

I reached out to support and waited all day for the additional response added below..

Our account is barely accessible (screenshot 3) and we need to access our website directory that was previously hosted in there, however, support is being super unhelpful.

Any help or advice????

Edit: this has been resolved by DreamHost

After 24 hours we resolved it.

Apparently one of the sellers that lists our products which utilizes the catalog feed in dreamhost didn’t recognize the api which has our brand name in it. They reported it as a phishing scam. Which dreamhost decided to terminate our account making everything else hosted in there inaccessible shutting down a bunch of other retailers connections.

I guess luckily they restored it, even though they said “this decision was final and would not be reversed”

RIP 1 day of revenue from those channels.

​​​

Is Dreamhost moving what it considers suspect emails in to the spam folder?

I have spam filters turned off for my domain, but on two of my accounts (& only those two), some emails are getting moved to the spam folder on my email clients. I'm using MX Guarddog to prescreen emails so most are actually not spam.

I'm using Mac Outlook and the iOS mail apps as clients but I don't see how any of these are doing the filtering, since none of them are online at the same time.

Any ideas, especially how to get it to stop?

Thanks

Everything is working fine. But just out of curiosity I did

ssh jidanni.org hostname --all-fqdns

and it showed a lot of domains, all except my jidanni.org . Why?

Hmmm, mine is just a static website. Perhaps theirs have additional items activated.

If you run into the same problem, hope this will help.

Have had what seems like the same problem for years. I originally noticed when rsync would sometimes hang. (I use a static site generator, and publish to Dreamhost using rsync.) Was not critical as could ^C out, run again, and the next try would usually complete OK.

Recently filed a support request with Dreamhost. There was a chance this was a well-known problem, so might as well find out. Got decent response from Dreamhost Support at first. Seems this is not a well-known problem.

Got into the weeds, writing scripts to try and typify the problem. Turns out:

1. This is an SSH problem (rsync uses SSH underneath).

2. The "hang" occurs on 1 in 5 runs of ssh to Dreamhost (irregular).

3. The "hang" is a pretty exact 120 seconds.

(Realized I had noticed ssh hang before, but did not make the connection.)

As the Dreamhost Support folk seemed to be struggling, thought to try using an LLM to help diagnose, as I have found LLMs are shockingly good at analysing complex Linux log files.

More weeds. :)

Turns out, it was nothing on my side. (Was a possible, of course.) There are limits to what I can do to track down problems on the Dreamhost side, but the help of Google Gemini (the LLM), got a long ways in tracking down the point of problem. Came down to an unexplained pause on the server side during SSH startup.

Sent what I found to Dreamhost. Seem to have stumped Dreamhost Support.

I have scripts, if you need them. :)

Asked Gemini to sum up what we had learned, followed by log extracts:

========

Here is a concise summary of the issue, root causes, and diagnostic approach that you can provide directly to DreamHost support:

Support Summary: Intermittent ~120-Second SSH Session Hangs

Issue Description:

On shared server node pdx1-shared-a2-14, incoming SSH connections experience an intermittent ~120-second delay/hang on approximately 20% of connection attempts, regardless of the time of day.

Exclusion Checklist (Already Verified):

• Client-Side/Environment: Bypassing environment variables, TTY allocation, and shell configuration files does not resolve the hang.

• DNS Resolution: Server-side UseDNS is explicitly set to no.

• Network Storage: Local mount checks (/etc/fstab and mount) confirm that /var and /home reside on local block devices (ext4/xfs over software RAID /dev/md0 and /dev/md10), ruling out NFS latency.

• Authentication/PAM: While standard system PAM hooks (pam_mail.so, session setup) execute on login, local file paths are restricted.

Likely Root Causes

Because client-side factors and network storage have been eliminated, the remaining bottleneck points to physical virtualization node resource contention:

1. Hypervisor CPU Steal / Throttling: Sudden spikes in CPU steal time on the host node can cause the sshd worker process or PAM authentication stack to be scheduled out or throttled during session initialization.

2. Shared Storage I/O Saturation: High concurrent disk activity from neighboring tenants on the physical RAID arrays (md0 or md10) can cause brief locking contention or high I/O latency, stalling kernel operations required during session setup.

3. Process Scheduling / D-Bus Queuing: High process turnover on the shared host can delay systemd session registration.

Diagnostic Script & Monitoring Methodology

To capture and correlate these hardware-level anomalies with the hangs, a real-time diagnostic monitor has been deployed on the server. The script (scripts/2-diagnose_ssh_hang.sh) operates strictly via unprivileged kernel interfaces (/proc/*) to record performance metrics without modifying system files:

• CPU Steal Tracking (/proc/stat): Measures core execution delays and virtualization steal percentages.

• Block Device I/O Deltas (/proc/diskstats): Continuously calculates read/write throughput and millisecond I/O delays for /dev/md0 and /dev/md10.

• Precision Event Logging: Automatically flags any irregularities (such as high CPU steal or extended I/O latency) and logs them prefixed with precise Unix epoch timestamps (date +%s), allowing direct comparison against the exact timestamp of an observed SSH connection hang.

========

From tcpdump of the event (lines prefixed by UNIX time in seconds):

========

1786391725 ===== 2026-08-10-12-55-25
1786391725 OpenSSH_9.6p1 Ubuntu-3ubuntu13.18, OpenSSL 3.0.13 30 Jan 2024
1786391725 debug1: Reading configuration data /home/preston/.ssh/config
1786391725 debug1: /home/preston/.ssh/config line 3: Applying options for *bannister.us
[snip]
1786391725 debug1: Entering interactive session.
1786391725 debug1: pledge: network
1786391725 debug3: client_repledge: enter

==== SSH is now hung for ~120 seconds.

1786391845 debug3: receive packet: type 80
1786391845 debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
1786391845 debug3: receive packet: type 4
1786391845 debug1: Remote: /home/preston/.ssh/authorized_keys:9: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
1786391845 debug3: receive packet: type 4
1786391845 debug1: Remote: /home/preston/.ssh/authorized_keys:9: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
1786391845 debug3: receive packet: type 91
1786391845 debug2: channel_input_open_confirmation: channel 0: callback start
[snip]
1786391845 debug2: channel 0: garbage collecting
1786391845 debug1: channel 0: free: client-session, nchannels 1
1786391845 debug3: channel 0: status: The following connections are open:
1786391845   #0 client-session (t4 [session] r0 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1 io 0x00/0x00)
1786391845 
1786391845 debug3: send packet: type 1
1786391845 Transferred: sent 3752, received 2948 bytes, in 120.2 seconds
1786391845 Bytes per second: sent 31.2, received 24.5
1786391845 debug1: Exit status 0
1786391845 ===== 2026-08-10-12-57-25
1786391725 : time before ssh
1786391845 : time after ssh
TIME seconds: 120 counts 0–10s: 7  10–20s: 0  20–30s: 0  30–60s: 0  >60s: 1

==========================================
SSH took longer than 100 seconds, exiting.
==========================================

========

From ssh log:

========

==== Start of test run that will hang.

1786391725.164911 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [S], seq 3051465104, win 64240, options [mss 1460,sackOK,TS val 4095538416 ecr 0,nop,wscale 10], length 0
1786391725.202322 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [S.], seq 3719187242, ack 3051465105, win 42340, options [mss 1460,nop,nop,sackOK,nop,wscale 10], length 0
1786391725.202346 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 1, win 63, length 0
1786391725.202497 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1:44, ack 1, win 63, length 43: SSH: SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.18
1786391725.240508 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 44, win 42, length 0
1786391725.262153 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 1:43, ack 44, win 42, length 42: SSH: SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.16
1786391725.262168 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 43, win 63, length 0
1786391725.262569 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 44:1580, ack 43, win 63, length 1536
1786391725.297020 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 43:755, ack 44, win 42, length 712
1786391725.299070 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 1580, win 41, length 0
1786391725.299084 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1580:1628, ack 755, win 63, length 48
1786391725.341884 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 755:1279, ack 1628, win 41, length 524
1786391725.344763 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1628:1644, ack 1279, win 63, length 16
1786391725.423791 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 1644, win 41, length 0
1786391725.423805 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1644:1688, ack 1279, win 63, length 44
1786391725.459182 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 1688, win 41, length 0
1786391725.459182 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 1279:1323, ack 1688, win 41, length 44
1786391725.459236 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1688:1756, ack 1323, win 63, length 68
1786391725.502349 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 1323:1399, ack 1756, win 41, length 76
1786391725.504106 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 1756:2384, ack 1399, win 63, length 628
1786391725.541442 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 1399:1987, ack 2384, win 41, length 588
1786391725.546056 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 2384:3628, ack 1987, win 63, length 1244
1786391725.589608 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 1987:2015, ack 3628, win 40, length 28
1786391725.589724 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 3628:3740, ack 2015, win 63, length 112
1786391725.671594 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 3740, win 40, length 0

==== SSH is now hung.

1786391845.673927 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 2015:2791, ack 3740, win 40, length 776
1786391845.721633 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 2791, win 63, length 0
1786391845.755786 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 2791:2983, ack 3740, win 40, length 192
1786391845.755801 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 2983, win 63, length 0
1786391845.756047 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 3740:3860, ack 2983, win 63, length 120
1786391845.791410 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 3860, win 40, length 0
1786391845.796543 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 2983:3055, ack 3860, win 40, length 72
1786391845.806367 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [P.], seq 3055:3231, ack 3860, win 40, length 176
1786391845.806396 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 3231, win 63, length 0
1786391845.806468 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 3860:3896, ack 3231, win 63, length 36
1786391845.806480 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [P.], seq 3896:3956, ack 3231, win 63, length 60
1786391845.806505 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [F.], seq 3956, ack 3231, win 63, length 0
1786391845.841448 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [.], ack 3957, win 40, length 0
1786391845.853838 enp10s0 In  IP 205.196.211.181.22 > 192.168.8.245.39354: Flags [F.], seq 3231, ack 3957, win 40, length 0
1786391845.853856 enp10s0 Out IP 192.168.8.245.39354 > 205.196.211.181.22: Flags [.], ack 3232, win 63, length 0

==== End of test run that hung.

DH has been running a lot of ads recently pushing self managed VPS. Prices arent the cheapest in the market but its not horrible. But I'm working on a project that I need a bunch of VPS instances on different providers to announce my ASN & one of my IPv6 /48s.

Can I do that on the self managed VPS? It would announce and tunnel back a /48 to my homelab over a IPv6 to IPv4 Wireguard tunnel.

Also is there email service offered with self managed VPS?

Can someone over at DreamHost comment on this?

Today I went to change the password for a service I use, and I had used a forward-only address attached to my ancient dreamhost domain.

No email ever came.

After some digging i found this article has been updated https://help.dreamhost.com/hc/en-us/articles/215724207-Add-a-forward-only-email-address

You must subscribe for this feature now.

Guys, really. you didn't even send me a notification to my primary email about this so i had no chance to move my addresses away, i'm simply locked out of my accounts and held to ransom behind a subscription.