Myrthos, 7 months ago

@AdamBishop I had an issue like that on Linux when my browser automatically changed http://localhost:1313 to https://localhost:1313 after a browser update. Obviously the https page does not exist.

AdamBishop, 7 months ago

@Myrthos I suspected that was a problem too, and I checked, deleted the cache and data, and tried various browsers, but to no avail. Thanks for the suggestion!! 🙏

simonemargio, 7 months ago

@AdamBishop Strange, I have been using Hugo on macOS for years and it has never given me any problems.

However, in addition to the advice they gave you, did you configure the config file correctly by specifying baseURL and theme?

Depending on the configuration of the first parameter you can have localhost:1313/some-text

_daniel, 7 months ago

deleted_by_author

AdamBishop, 7 months ago

@_daniel Thanks Daniel! I checked, it's there, so, unfortunately, that isn't the problem 😕

jrfern, 7 months ago

@AdamBishop
Port 1313 blocked, maybe?

AdamBishop, 7 months ago

@jrfern Thanks JR! I'll check if anything is hogging or blocking the port. Though I can't imagine why. There's no firewall or other software in particular running...

I'll try "$ lsof -i tcp:1313" when I get a chance!

jrfern, 7 months ago

@AdamBishop
My Linux mind tells me that the answer is written in the logs - no idea about logs in a Mac

AdamBishop, 7 months ago

@jrfern Perhaps I could try "$ hugo server --verbose" or "$ hugo server --verboseLog". Thanks JR!