diff --git a/docs/latest/SUMMARY.md b/docs/latest/SUMMARY.md index 62c4a4c47..1009abab0 100644 --- a/docs/latest/SUMMARY.md +++ b/docs/latest/SUMMARY.md @@ -7,7 +7,6 @@ - [Data Source](essentials/data-source.md) - [Configuration](essentials/configuration.md) - [Translating](essentials/translating.md) - - [Troubleshooting](essentials/troubleshooting.md) - [Contributing](contributing/index.md) - [Continuous Integration](continous-integration.md) diff --git a/docs/latest/essentials/troubleshooting.md b/docs/latest/essentials/troubleshooting.md deleted file mode 100644 index 01ed804e2..000000000 --- a/docs/latest/essentials/troubleshooting.md +++ /dev/null @@ -1,20 +0,0 @@ -# Troubleshooting - -Common GitHub issues that are not easily remedied with cleaner code or -documentation will be recorded here. Please feel free to make PRs to update this -page. - -## Common Problems - -| Problem | Most Common Reasons | -| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| ** Can't retrieve Study List over DICOMWeb** | 1. QIDO root URL is incorrect
2. DICOM Web is not enabled on PACS | -| ** Can't retrieve images** | 1. WADO Root URL is incorrect
2. DICOM Web is not enabled on PACS
3. HTTP Basic Authentication username and password are incorrect or not provided. | - -## Debugging Steps - -### Can't retrieve Study List over DICOMWeb - -1. Check that you can query your PACS using an alternative DICOM Web client - (e.g. cURL, or a Web Browser). If you cannot, then your PACS is configured - incorrectly. Refer to the documentation of the image archive. diff --git a/docs/latest/getting-started.md b/docs/latest/getting-started.md index db0216371..2c73d676f 100644 --- a/docs/latest/getting-started.md +++ b/docs/latest/getting-started.md @@ -91,9 +91,6 @@ yarn run build:package changing the Study Date filters to a wider range. - If you see a 'Loading' message which never resolves, check your browser JavaScript console inside the Developer Tools to identify any errors. -- If you see any errors in your server console, check the - [Troubleshooting](./essentials/troubleshooting.md) page for more in depth - advice.