question-mark
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.

No handler accepted "/"

See original GitHub issue

I’m trying to make ekg accessible out in the open on a server using

forkServer anIpAddress aPort

when visiting that ip address on that port I get No handler accepted "/". Is this expected? If so, how do I use ekg remotely?

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:18 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
dysingercommented, May 6, 2016

It might be better to use fileEmbed so that directories don’t need to be found.

3reactions
ods94065commented, Feb 27, 2016

Here’s my story while running into this problem:

I’m using Stack to build a web app (including ekg) that I’m deploying inside a Docker container. In particular, I’m installing my app in a fresh container with no explicit Haskell dependencies (we’ll see how that goes!). JSON API calls to EKG worked but HTML did not.

The problem was indeed that the directory of assets didn’t exist in the runtime container, and ekg could not find it. This directory contains the files needed to provide the HTML interface, and Snap apparently raises this error when a file it’s trying to serve can’t be found (see https://github.com/snapframework/snap/issues/102 ).

The problem Sean mentions in https://github.com/tibbe/ekg/issues/48 bit me hard, since if his path to the assets directory was weird, mine using Stack/Docker is really weird. I don’t know an easy way to magic these files into my Docker installation, so I cheated: I’m pinning the ekg version for now and copying the assets/ directory into my project.

One final note: You’ll see that ekg appends </> assets to your data directory, so make sure you’re not setting your data directory to the assets directory itself! I installed my stuff in /app/ekg-0.4.0.9/assets, and set ENV ekg_datadir=/app/ekg-0.4.0.9 in my Docker container. That was what did the trick.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Pact ToDo MVC - No handler accepted "/" Message in Browser
1 Answer 1 ... server.conf file configures the port for the pact server, but the web app will be running on a node...
Read more >
Pact ToDo MVC - No handler accepted “/” Message in Browser
Hi, server.conf file configures the port for the pact server, but the web app will be running on a node server and the...
Read more >
400 - "No handler found for..." - Trying to understand JSON ...
I think the 400 response is being sent by Moodle to Cengage as mod/lti/services.php can return this message: 72 $response->set_reason("No ...
Read more >
No handler was found for message type 'Microsoft.M...
Error Message: No handler was found for message type 'Microsoft.Mashup.Evaluator.MessageBasedOutputStream+BinaryChunkMessage'. Stack Trace:
Read more >
Solved: {"error":"no handler found for uri [/metadata/item...
Solved: Hello everyone, When setting up Geoportal 2.6.5 with ElasticSearch 8.1.3 on a Windows 10 VM, I followed the installation steps ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found