Hyper V setup, remove port number in URL

Hi, I used to have DevKinsta installed (Windows 11) using WSL 2 (Docker). Though this worked, it was terribly slow.

Then I switched to Hyper V (Installed the Hyper V service), and wordpress performs how it used to be.

Thing is, my URL now has a port number. http://pwp-website.local:62170/

In my WSL 2 setup, this portnumber was not present.

Activating Elementor Pro, I get an error. Elementor support indicated this is due to the port number behind the URL.

Is there any way to configure Hyper V / Docker / DevKinsta to not have this port number, so I can activate my Elementor Pro license again?

Thank you!

Hi @jwhennink, thanks for reaching out!
Please go to your DevKinsta settings page and manually change the ports to 80 and 443:

If it complains about those ports being in use, you might have another application using them.

thnx Kevin for your quick reply!
I get the following error (all my sites are stopped):
Do you know how to fix?

That’s a new one; I’ve never seen that error before. Can you please privately share your main.log file with me?

Hi Kevin, PM has been sent!
Thanks a lot!

1 Like

Thanks for that @jwhennink!
So the errors are definitely because of the switch to Hyper-V. Your old databases for previous sites still exist if you switch back to WSL2 but they don’t exist under Hyper-V.

The process is trying to backup all of your sites but is running into a database connection error for the sites that you had under WSL2.

So you have a few options.

  1. You can switch back to WSL2 then delete your sites from DevKinsta before switching back to Hyper-V(this would be best for the longterm).


  1. If you are comfortable with editing JSON, you could edit your config.json and manually change the Ports (C:\Users\USERNAME\AppData\Roaming\DevKinsta\config.json):
    Note that doing this would skip the step that takes a backup and runs a search and replace for the port number in your databases. You would have to do that manually as well. Also be sure to completely close DevKinsta from the Task Manager before starting it up again after you edit this file.


  1. Push any sites you have right now to Staging(or make backups of them), then reset Docker and completely uninstall DevKinsta so that you start fresh:
    Uninstall DevKinsta

The main issue is that Docker keeps the WSL and Hyper-V database volumes separate.

Kevin, you are amazing!

I went for option 1, switched back to WSL 2 and deleted all sited created with WSL 2.
Then switched back to Hyper V and changed ports.
This process went great now, without errors.

Then I could start my site (now without port number postfix) and was able to activate Elementor Pro.

Thanks a million!

Now I have a lot of work to catch up!!


1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.