@thphuc - when you run the forem software locally (which looks like it started up correctly) the software is in "development" mode - and some error handling that would normally have occurred (in this case, redirecting back to sign in when trying to access pages that require login) is disabled, the idea is a developer would like to see the actual error and where it happened, while in "production" mode the errors would expose too much of the internals to be useful to most users, for example the same link in DEV.to for me gives a 404 error page.
You'll want to log in (the database seed created a few users, all with password "password", the administrator account has email "admin@forem.local" - once you log in, following that link will work without raising the authorization error.
@thphuc - when you run the forem software locally (which looks like it started up correctly) the software is in "development" mode - and some error handling that would normally have occurred (in this case, redirecting back to sign in when trying to access pages that require login) is disabled, the idea is a developer would like to see the actual error and where it happened, while in "production" mode the errors would expose too much of the internals to be useful to most users, for example the same link in DEV.to for me gives a 404 error page.
You'll want to log in (the database seed created a few users, all with password "password", the administrator account has email "admin@forem.local" - once you log in, following that link will work without raising the authorization error.
Thanks @ellativity and @djuber . I think I should follow the instructions from @djuber first. I will let you know if I see any other issue.