I've installed gCn and I'm running Doors CS 7.4 on my ti84+. I type in to the command prompt:
"...gcnclient -n WebHub -l HowdyElvira (don't worry about it) -d d"
and it responds
"Info: Using default server host gcnhub.cemetech.net
Info: Using default port 4295
"
then I open up gossamer and nothing happens.
I'm on windows, I installed the USB filter for direct USB, I restarted my computer, idk
It's stuck on loading page.


Edit: bump? idk its at the top but noone is replying. Any solutions? Even your craziest!?

Please don't double post by sending two posts in a row within a 24-hour period.
You'll probably just need to be patient - the topic is barely three hours old; if nobody's responded yet, it likely means that nobody who has seen the post so far has known the answer. There are many people who only check the forums once per day or even less frequently than that, so give them a chance to see your post and write a response to it.

The Gossamer web bridge (WebHub) hasn't been online for a while now, so it's expected that Gossamer won't work because the server it depends on doesn't currently exist.

At this point it needs to be rewritten, or you might be able to faff about with the old implementation enough to get it limping along.

Grr. I want code written 15 years ago (maybe less i dont actually know) to function NOW!

when you say "faff about"... I'm not actually skilled in any coding language besides scratch and TIBasic(barely). What do you mean (more specifically)?

There doesn't seem to be anything particularly gnarly in there, but I expect the gcnweb script will still only work with Python 2 and it calls out to lynx to render web pages, so at least you'd need to get an obsolete version of Python and a copy of lynx in order to run it.

No promises since I haven't tried to run it myself, but if you can satisfy those requirements I think it should be runnable.

Note that it would be moderately unsafe to connect that bridge to a publicly-accessible hub, because it doesn't even attempt to limit the addresses a client can connect to so anybody able to send requests to it could access services on your computer or local network that aren't meant to be accessible to the public. That's one of the major barriers to re-deploying this bridge: it behaves like an open proxy, and must be carefully firewalled to avoid exposing private networks to the public.

how would I firewall it? It suddenly doesn't seem like a good idea...

be back in 8 hrs its 9:12PM Eastern Time