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.

Oops, looks like there's no route on the client or the server for url: "http://my-domain.com/dicom-app-viewer"

See original GitHub issue

I need to deploy a standalone-viewer to my production server.

I’ve did everything like described in this article - https://github.com/OHIF/Viewers/wiki/Running-and-building-the-Standalone-Viewer

But when I navigate to http://my-domain.com/dicom-app-viewer I get error:

Oops, looks like there's no route on the client or the server for url: "http://my-domain.com/dicom-app-viewer."

I’ve compiled my application using this command: METEOR_PACKAGE_DIRS="../../Packages" meteor-build-client dicom-app-viewer -u http://my-domain.com/dicom-app-viewer (as described in article above).

What am I doing wrong?

P.S.: What I need in the end:

I have a server application which will be used to provide an api for viewer.

Also how to configure viewer to make requests to specified url to get json with list of dicom files?

Issue Analytics

State:
Created 6 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

nasu38yencommented, Nov 15, 2017

I tried it again. This displayed no problem. http://localhost:3000/subdirectory/?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/sampleDICOM.json However, this is a load error. http://localhost:3000/subdirectory/sampleDicom.js

I feel like, use clinical.route instead of iron.route solve this problem. How is that? https://github.com/iron-meteor/iron-router/issues/1454

0reactions

dannyrbcommented, May 6, 2019

It looks like this issue has been resolved. If any of you are still experiencing it, please feel free to create a new GitHub issue with the steps to reproduce or a minimal reproduction in a separate repository that you can link to.

Top Results From Across the Web

LesionTracker error "Oops, looks like there's no route ... - GitHub

It builds successfully but gives the error "Oops, looks like there's no route on the client or the server for url: "http://localhost:3000/", ...

How to Fix Discord's “No Route” Error - Help Desk Geek

Discord displays a “No Route” error when the client can't successfully connect to a voice channel. This usually happens when your network ...

Ironrouter says route doesn't exist when it does ("Oops, looks ...

However, when I access http://localhost:3000/test/123 I get the following error message: Oops, looks like there's no route on the client or the server...

How to Fix No Route Error on Discord - Appuals.com

In all cases, Discord is being stopped in its tracks when trying to connect to a voice server. What is Causing the Discord...

Oops, looks like there's no route on the client or the server for url

Hi, please help here is my code I'm not sure why it is not getting the id: Template.chats.helpers({ currentId: function() { return ...