Cannot access any file in a public folder through url in web Browser
node:~# nslookup keybase.pub Server: 1.1.1.1 Address: 1.1.1.1#53
Non-authoritative answer: *** Can't find keybase.pub: No answer
Thanks for replying @zikorayann
This can help too https://news.ycombinator.com/item?id=34709699
This issue should be closed, since from March 1, 2023 onwards, keybase.pub has been shut down (and therefore there will not be any domain name resolution for it any longer):
We regret to inform you that the Keybase.pub web hosting service will be shutting down on March 1, 2023. Although the service was a great showcase for the kinds of cool things that could be built with Keybase, the usage of this product never took off. The continued cost of maintaining the site has led us to make the difficult decision to shut it down. If you are hosting any content on Keybase.pub, we strongly recommend moving that content to a new hosting provider as soon as possible.
No Keybase Filesystem (KBFS) data will be removed from any user public folders. All data will remain safe and viewable by others running Keybase. Other features of Keybase including Chat, KBFS, Teams, Git, Wallet and others will continue to run normally as well.
-Keybase
(originally posted on keybase.pub; retrieved on 2023-03-20 from Reddit)
The app should reflect this change too. Now it still states these files are public.
Well if anything, It's still possible to create your own "keybase.pub" site. It's funny that android app, keybase book still mention now non existent feature.
I Just did experiment on arm64 (had to self compile keybase and kbfs) + and pretty much stock ubuntu nginx, and well, it can be used as website host (
@dw5 that should work — but it would require Keybase's written approval, since such a project would be using Keybase's trademark (but would be run by the community instead).
@dw5 that should work — but it would require Keybase's written approval, since such a project would be using Keybase's trademark (but would be run by the community instead).
The closest I've found to an official policy on this from Keybase is in an issue comment here. Looks like as long as you're clear that it's a community project using Keybase and not run by Keybase it's probably fine, which is what I would expect anyway. Just make the actual name of the site derivative with a powered by Keybase subscript.