some http connections load indefinitely on localhost, starting with lima 1.1.0

[rpkoller]

Description

In the context of using the latest version of lima (1.1.1) in combination with DDEV (HEAD) and ngrok (3.23.3) i'Ve noticed a problem when i've tried to share an install of drupal in a video call for other attendees. something that worked flawlessly for months and years. noticed it the first time in the meeting last week and again yesterday. i havent used the share functionality the weeks before - so i was not sure when it stopped working .

problem is you are able to access the front page via the link provided (https://nnnn-nnnn-nn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn.ngrok-free.app), but if you try to log in by clicking the login link, either accessing the login page loads indefinitely (https://nnnn-nnnn-nn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn.ngrok-free.app/user/login) or sometimes you are able to access the login page but entering the login credentials and pressing the submit button then leads into the indefinite loading. the traffic inspector on ngrok returns "ngrok error" 3004 and or 3200 on the attempts...

so at first the suspicion was the problem was rooted in the context of ngrok. but locally the ddev project is accessible with https://myproject.ddev.site which works flawlessly BUT the host is also accessible via 127.0.0.1 and a particular port for the project at hand, so for example https://127.0.0.1:32769 . and accessing a running project via that https://127.0.0.1:32769 link you run into the exact same issue experienced with ngrok when you try to access (https://127.0.0.1:32769/user/login) and/or try to log in on that page . so it looks like a problem with lima itself.

i went ahead and tested with previous versions. the problem is not reproducible and everything works as expected with lima 1.0.7, the problem was introduced with lima 1.1.0.

apologies for that vague outline of the things we've observed, cuz i am still unable to clearly articulate what the root cause is nor how come up with a reduced test case that does not need something like ddev. ( i even struggle to come up with an appropriate title for the issue :/)

Update: I've realized i still had colima 0.8.1 installed that is using lima 1.1.1 as a dependency. i've uninstalled the version of lima head and switched back to lima 1.1.1 and spun up an instance of colima again. within colima 0.8.1 using lima 1.1.1 i am unable to reproduce the problem i run into with limactl alone. puzzling why that is the case but i think that is another noteworthy detail.

[balajiv113]

Can you try it with current master ?? We recently fixed a grpc port forwarding issue

[rpkoller]

thanks for the headsup! built the latest state of head (unlinked my stable install with homebrew on macos and then did brew install --head lima):

$> limactl --version
limactl version 1.1.1-141-ge05d7821

but problem is it is not fixing the problem. when i try to login on the login page it loads indefinitely locally with 127.0.0.1:32769 :(

[rpkoller]

updated the issue summary with another important detail - colima that is using lima is not affected by that issue.

[AkihiroSuda]

Colima is not affected because colima still uses LIMA_SSH_PORT_FORWARDER=true by default
https://lima-vm.io/docs/config/port/

[AkihiroSuda]

Possibly related:

• [gRPC portfwd] client connection is not closed immediately when server closed the connection #3685

[rpkoller]

at first congrats and thank you for the 1.2.0 release! i'Ve just upgraded to the stable homebrew version. as mentioned above i've tested the HEAD version a few days ago which hasnt fixed the problem. since then only #3708 got one, but that is only CI related. but the odd thing i am unable to reproduce the bug anymore in my test setup. with the following testing steps i was able to reproduce the problem 100% (step 1 to 4 was only necessary once, for retesting i only need to do step 5 to 7)

1. Install DDEV: https://ddev.readthedocs.io/en/stable/users/install/ddev-installation/
2. git clone git@github.com:ddev/d11simple.git drupal11 && cd drupal11
3. ddev config --host-webserver-port=33999
4. ddev drush si --account-name=admin --account-pass=admin -y
5. paste 127.0.0.1:33999 into your browser
6. click the login link in the upper right corner
7. either already there, or if you try to log in with the user name admin with the password admin the indefinite loading happens when pressing the submit button

but that is working now?! to make sure that the ssh port fowarder isnt active i also did limactl ssh default and then echo $LIMA_SSH_PORT_FORWARDER where i got an empty output. so that means nothing is set and lima is using the default false. so i am using gRPC still and the error is gone. it is just odd that the problem is gone even though the CI issue was the only in relation to port forwarding that got fixed since the last time i tested?

[jandubois]

it is just odd that the problem is gone even though the CI issue was the only in relation to port forwarding that got fixed since the last time i tested?

I don't think so, the PR to fix the CI issue also fixed #3685, which @AkihiroSuda mentioned as "possibly related" above. I guess this can now be upgraded to "obviously related". 😄

So maybe do some more testing, and then close this issue if the problem can no longer be reproduced.

[rpkoller]

@jandubois ohhhhhh i completely misread #3708 then. i thought it was solely about fixing something in the CI process but as you said it also contained a fix for #3685 . Yep then #3708 also fixed this issue. Tested several times with different projects over the evening, via the port locally (127.0.0.1:xxxxx) as well as via ngrok. everything is working as expected still. so this issue can be considered fixed as well. thanks again!