Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
UI thinks my daemon isn't running
See original GitHub issueAfter running npm install and npm start, the web ui tells me Failed to get configured IPFS gateway. Is the IPFS daemon running? and Failed to determine local IPFS version. Is the IPFS daemon running?. My daemon is running, and I have the companion on and working. What could be causing this error?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Can a X client (or a process running a GUI program) be a ...
The big problem here comes when your system runs a graphical environment. Since GUI programs (i.e. Chromium) are not attached to a terminal, ......
Read more >don't show an instance warning for daemon not running if no ...
currently, I think most peoples' first experience with dagit involves a warning.
Read more >How to use GUI (ie not terminal) with daemon? : r/DoomEmacs
When I say "GUI" I mean "not terminal." Maybe that's just wrong and so this can't be done.
Read more >Airflow dags are not recognised when running the webserver ...
I think this problem arises from the fact that the webserver has a different configuration when being run as a daemon compared to...
Read more >GUI does not start - Ask Ubuntu
10 Answers 10 · Press Ctrl Alt F7 · Press Alt F2 · Log in via terminal · Go to /etc/X11 and delete...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It could be a CORS issue… have you added CORS config as per https://github.com/ipfs-shipyard/ipfs-webui#config-your-ipfs-daemon
Are you running your ipfs daemon with the default config? When you run
ipfs daemonwhat is listed out as the API address? Do you see:CORS, good point.
I’m trying share.ipfs.io without npm but I got the same error at stock IPFS webiu, localhost:5001. So I add it also into the CORS origin: