I'm going through the getting started page of the project, and after running nc -l 4444 for portsinuse.sh, I can't seem to connect to the localhost:4444. Also, for the buildtransperthtimetables.sh, after making the file executable and running it, it gives me a cannot read calendar.txt

I managed to get the transperth timetables working, but I can't seem to get the portsinuse to work

ANONYMOUS wrote: That's very odd - which platform? Wondering if you don't have a name mapping to 127.0.0.1 (which would be odd). Can you access - 127.0.0.1:4444 ?? Ahh, that's where I got up to yesterday before going home; I've marked it as 'Under Construction' and will get back to it today (wondering if any file-format has recently changed; hope not).

ANONYMOUS wrote: Great - what was missing, or what did you have to correct?

I think it was when I downloaded the files, the calendar.txt was missing (for some unknown reason), so I went back and downloaded it again and checked the files.

So after running nc -l 4444, I get this output in terminal: GET / HTTP/1.1 Host: localhost:4444 Connection: keep-alive sec-ch-ua: "Google Chrome";v="123", "Not:A-Brand";v="8", "Chromium";v="123" sec-ch-ua-mobile: ?0 sec-ch-ua-platform: "macOS" Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36 Sec-Purpose: prefetch;prerender Purpose: prefetch Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7 Sec-Fetch-Site: none Sec-Fetch-Mode: navigate Sec-Fetch-User: ?1 Sec-Fetch-Dest: document Accept-Encoding: gzip, deflate, br, zstd Accept-Language: en,zh-CN;q=0.9,zh;q=0.8 Cookie: PGADMIN_LANGUAGE=en; username-localhost-8888="2|1:0|10:1713009326|23:username-localhost-8888|196:eyJ1c2VybmFtZSI6ICJhMzU4NzE4NmJlYjk0ZDA4Yjc3OGZkM2U0NGMyMmJjMCIsICJuYW1lIjogIkFub255bW91cyBTaW5vcGUiLCAiZGlzcGxheV9uYW1lIjogIkFub255bW91cyBTaW5vcGUiLCAiaW5pdGlhbHMiOiAiQVMiLCAiY29sb3IiOiBudWxsfQ==|6bd03e876946f6aff9f94084121db9bd6e9b9738618f6d2dd466c27f749945c0"; _xsrf=2|aada6237|2ace50e5ac0330c2f76e4631a9480545|1713009326 And going to the localhost4444 it says "The site can't be reached" and "localhost refused to connect"

ANONYMOUS wrote: Yes, that's exactly as expected. That is what the web-browser is sending the the 'nc' process, which is listening on port 4444. Probably because you're missing the colon before the 4444.