Serving an app with basic interactivity fails

[cstjean]

(Disclaimer: this is one of those "This is so simple it can't possibly be a bug; I must be doing something wrong" issue, but since discourse had nothing to say, I'm reporting it here)

This simple code:

using Bonito, Bonito.Observables
import Bonito.TailwindDashboard as D

app = App(DOM.div(D.Slider("nsamples", 1:200, value=100)), title="hello world")

port = 9384
url = "0.0.0.0"
server = Bonito.Server(app, url, port)

Works fine on http://localhost:9384/

but the interactivity fails and the visual aspect is off on http://my_ip:9384

@etpinard reports that

pops up in the dev tools. When served, the app should not look up anything in localhost.

[SimonDanisch]

You need to set the proxy_url:
https://simondanisch.github.io/Bonito.jl/stable/deployment.html#Proxy-Julia-Hub

[cstjean]

Thank you for the answer. I tried today for the second time to follow this advice, and I'm still stuck with the same behaviour. I tried adding the

server.proxy_url = ".../$(server.port)"

line, no luck. I don't understand why a proxy is involved if I'm entering my own IP address. It looks from my searches online that the request does not leave my computer at all in that case. Furthermore, I tried:

C:\Users\abcde>netsh winhttp show proxy

Current WinHTTP proxy settings:

    Direct access (no proxy server).

Though apparently it's not that reliable.

Genie works out-of-the-box for me, even on my own IP, with no proxy configuration. Is it using a different technology?

EDIT: perhaps important to note that I am working in a harsh IT environment, so these failures are not unexpected.

[cstjean]

server = Bonito.Server(app, url, port, proxy_url="http://server.ip.address:$port", verbose=0) worked out for us.

Looking at the docs again:

Is that what the ... is supposed to mean? Like: "Replace ... with your own IP/server address"? I thought .../$(server.port) was meant to be copy-pasted verbatim. 😓 I can make a PR to clarify the docs if anyone can confirm.

[cstjean]

Correction: it works in Firefox and in Chrome, but in Edge styling is off and it is not interactive (though it works fine on localhost). There's a decent chance that Edge has been gimped by the IT department, but if anyone else has had issues with Edge, please let me know.

[cstjean]

Resolution: some internal IT rule had Edge running it in IE-only compatibility mode, which of course ruined it.