Setting block=False at eel.start() gives error

Eel version 0.14.0

Describe the bug When the app is started with block=False, It gives the error as Error site can't be reached Issue similar to this one: #167

To Reproduce Steps to reproduce the behavior: try to start the app with eel.start("index.html",block=True) As show in the code snippet below:

import pyautogui
import eel
import datetime
import time
eel.init('front-end')
#--------------------------------------------------------------------------
#Problematic line
eel.start('index.html',size=(500,500),block=False) 
#this works fine as long as it is started without the block=False
#--------------------------------------------------------------------------
@eel.expose
def handshake(secs):
    secs=float(secs)
    while secs:
        eel.sleep(1)
        pyautogui.press('f15')
        
        print(f"Time: {datetime.timedelta(seconds=float(secs))}")
        return f"Time: {datetime.timedelta(seconds=float(secs))}"

Expected behavior The app should work normally but it gives LocalHost error

Screenshots

Desktop (please complete the following information):

• OS: windows 11
• Browser Google Chrome

[bernardolansing]

Hello @thatfloflo. Thank you for sharing your solution. For me, it worked but only for the first time I ran my code. After that, localhost would be refused again. But you gave me the ideia to use eel.sleep(1.0) just after eel.start being called. I am not sure about the 1.0, but this way it started to work, at least for me. Worth trying.

Update: nah, this just makes it load the html, but JS is still not loaded, no matter what time interval I choose to eel.sleep. Does anyone have any tip? I really need to get this working soon…

[thatfloflo]

I suspect your script might just finish and quit before you ever get around to connecting. Try something like this:

import eel
import gevent
eel.start('index.html',size=(500,500),block=False)
gevent.get_hub().join()

If you don’t have eel block then you need to make sure the event loop is entered yourself as far as I can tell. This also leaves it up to you to quit the event loop when the last socket is closed (or whatever conditions/events happen that should produce that behaviour).