[CYPRESS-2560] 504 error when trying to view local Cypress instance Created: 08/10/23  Updated: 09/20/23  Resolved: 09/20/23

Status: Closed
Project: CYPRESS Issue Tracker
Component/s: None

Type: Bug/Issue Priority: Moderate
Reporter: Steven Jones Assignee: David Czulada
Resolution: Resolved Votes: 0
Labels: None

Attachments: PNG File CaptureCypress504.PNG     PNG File CaptureCypressError1.PNG     PNG File CaptureCypressError2.PNG     PNG File CaptureCypressPortForward.PNG     PNG File CaptureMsInfo32-1.PNG     PNG File CaptureMsInfo32.PNG     PNG File UpdateCapture.PNG    
Cypress Version: Cypress v7.1.1

 Description   

After installing and running Cypress 7.1.1 VM via Virtualbox, I receive a 504 error when I attempt to access the site. I also receive a error when trying to create an admin user in SSH. Attached are screenshots of the errors and my port forwarding config.

I am able to host and set up previous Cypress version instances without issue.



 Comments   
Comment by Steven Jones [ 08/25/23 ]

I was able to successfully host Cypress v7.1.1 using Virtualbox on a colleague's machine that is identical to mine as far as hardware/OS. The only relevant difference I see is they don't get the "A Hypervisor has been detected..." message in systeminfo.exe/msinfo32.ex so I think I can narrow the issue down to my machine having some software or configuration that is still using hypervisor. I'll update the Jira if I'm able to find the culprit.

Thank you for all your help!

Comment by David Czulada [ 08/24/23 ]

Can you try pinging the Internet (from the VM) to see if you have internet access.

Pinging 8.8.8.8 (google's IP address) will let us know if your VM has access.

ping 8.8.8.8

If it doesn't work, you will likely need to configure your VM to work with your company's firewall.

Comment by Steven Jones [ 08/24/23 ]

I tried that exact sequence of steps and got the same result, its still showing 7.0.4. During the update, I did notice timeout errors in the log but the update seemed to progress and I never received a status message stating that the update failed.

Comment by David Czulada [ 08/24/23 ]

Steven-

2 thoughts on the upgrade path.

1) Try running the following command before running the script.

sudo apt update

2) Try restarting your VM after the upgrade.

-Dave Czulada

Comment by Steven Jones [ 08/24/23 ]

I tried the upgrade script route. but the version of Cypress still shows 7.0.4 afterwards. The log messages during the update seemed to indicate that an update was successful.

Is there any help on how to load the Cypress image on Docker? I've never used Docker and I'm not finding much help online for loading an *.ova image. 

I've tried VMWare, I was able to spin up the instance but I'm not able to figure out how to access the  Cypress Website since I don't know how to configure port forwarding in VMWare. I wasn't able to find much help online either.

AWS is a last resort due to cost.

 

 

 

Comment by David Czulada [ 08/18/23 ]

Steven-

I'm relatively certain that this is related to the hypervisor compatibility issue.

The major differences between Cypress 7.0.x and Cypress 7.1.0 is that the VMs for Cypress 7.1.0 are built on Ubuntu-22.04 vs Ubuntu-18.04 and have Mongo-6.0.6 vs Mongo-4.4.14.

If you are OK with running older versions of Ubuntu and Mongo you can always start from an older version of Cypress (v7.0.4 is our last built VM on Ubuntu-18) and run the upgrade script (https://github.com/projectcypress/cypress/wiki/Cypress-7.x-Upgrade-Instructions)

https://s3.amazonaws.com/cypress_public/Cypress.cypress_7.0.4_Public_VM.ova

We also have other installation routes (e.g., AWS and Docker) that could also work out for you.

Please note that if you go with running Cypress on Ubuntu-18.04, that version of the OS is no longer supported by Ubuntu.

-Dave Czulada

Comment by Steven Jones [ 08/18/23 ]

I'm still getting the same result. The wording in the error messages in my attached screenshots show "connection refused", are you certain this is related to a hypervisor compatibility issue? Has something security related changed in  7.1.1? All prior versions of Cypress are working in VM on my machine.

Comment by David Czulada [ 08/16/23 ]

Steven-

I've been trying (unsuccessfully) to recreate your scenario when us 'Hyper-V' disabled and getting prompted by Virtual Box to enable one of the virtualization options, VT-d, in my bios.

Note, the method I used to disable Hyper-V is

1) Open cmd using the Run as administrator option
2) run the command

bcdedit /set hypervisorlaunchtype off

3) Restart Windows

I'm also running Virtual Box version 6.1 (not sure if that makes a difference)

-Dave Czulada

Comment by Steven Jones [ 08/16/23 ]

Is there anything else I can try? 

Comment by Steven Jones [ 08/11/23 ]

Even after I disabled hyper-v, I'm still getting the same errors.

Based on my research,  hyper-v is still enabled if the status "A hypervisor has been detected..." appears in MsInfo32.exe (see screenshot). I was finally able to remove this status after disabling Hyper-v and virtualization options in my bios. Afterwards when I try to spin up the Cypress instance, VirtualBox displays an error that I need to enable one of the virtualization options, VT-d, in my bios. When I enable it, the "hypervisor has been detected" message reappears in MsInfo32.exe. 

Comment by Steven Jones [ 08/11/23 ]

Yes, Win10 64bit. I am currently working with IT support to disable Hyper-v on my machine. I'll give an update if this does the trick or not. 

Comment by David Czulada [ 08/10/23 ]

Steve-

Are you running this on a Windows machine? The Cypress v7.1.0 VM is built with Mongo v6 which is incompatible with Microsoft's Hyper-V (https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-windows/#virtualization).

To get the VM to work in Virtual Box you will need to disable Hyper-V. Microsoft offers this guidance
https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

Also, I've been successful do this by following the instructions for option 2 "2. How to Disable Hyper-V Using BCDEDIT" here (https://www.makeuseof.com/windows-11-disable-hyper-v/)

-Dave Czulada

Comment by Cypress Team (Inactive) [ 08/10/23 ]

Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day

Generated at Sun Aug 31 08:15:04 UTC 2025 using Jira 10.3.8#10030008-sha1:cdaed80cecc964184c5b19b002388d56f96e274e.