Skip to content

Commit c49af41

Browse files
jaboehrijaboehri
committed
Added redirect urls for fat ping and initial troubleshooting pages to point to
1 parent e0e464b commit c49af41

12 files changed

+74
-0
lines changed

‎docs/src/operations/troubleshooting/common-http-status-codes.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: Common HTTP Status Codes
3+
icon: support
4+
---
5+
6+
# 403 Forbidden
7+
This HTTP status code may be encountered in many different way in the context of the DSF:
8+
- Process plugin is not installed at FHIR server where the Task resource was posted
9+
- Client certificate of the FHIR server where the Task resource was posted is invalid

‎docs/src/operations/troubleshooting/connection-refused.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: Connection Refused
3+
icon: cog
4+
---

‎docs/src/operations/troubleshooting/connection-timeout.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Connection Timeout
3+
icon: time
4+
---
5+
6+
A connection timeout happens when a connection attempt is made but there is no response from the endpoint in a certain timeframe.
7+
There are many possible reasons for why this happens:
8+
- The server is currently down or unreachable due to network configuration
9+
- The server is under heavy load and thus unresponsive
10+
- Firewalls might be blocking outgoing connections to the server
11+
- Arbitrary network issues
12+
13+
If this is happens during the execution of a DSF process, it is recommended to try starting the process again to see if the issue persists. If the issue persists, it is recommended to ensure no firewall settings are blocking the outgoing connection attempt. If this is not the root of the issue, further troubleshooting has to take place that may have to include someone knowledgeable about the process plugin or someone from the team maintaining the server or a combination of both.

‎docs/src/operations/troubleshooting/read-timeout.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
title: Read Timeout
3+
icon: time
4+
---
5+
6+
A read timeout is a network error that usually happens when a resource is read from a server but the resource takes too long to arrive at the client.
7+
There are many possible reasons for why this happens:
8+
- The server unexpectedly went down during transmission
9+
- The server is under heavy load and unable to process the request in a timely manner
10+
- Arbitrary network issues
11+
12+
If this is happens during the execution of a DSF process, it is recommended to try starting the process again to see if the issue persists. If the issue persists, further troubleshooting has to take place that may have to include someone knowledgeable about the process plugin or someone from the team maintaining the server or a combination of both.

‎docs/src/operations/troubleshooting/ssl.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
title: SSL
3+
icon: lock
4+
---
5+
6+
SSL issues arise if there is a misconfiguration of client/server certificates.
7+
Client certificates may:
8+
- Be expired
9+
- Have an untrusted root
10+
- Be revoked
11+
12+
Server certificates may:
13+
- Be expired
14+
- Have an untrusted root
15+
- Be revoked
16+
- Have the wrong host as the subject
17+
18+
It is recommended to use [OpenSSL](https://openssl.org/) for further debugging.

‎docs/src/operations/troubleshooting/unknown-host.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: Unknown Host
3+
icon: question
4+
---
5+
6+
This error occurs if a host name cannot be mapped to an IP address. Either because of a spelling mistake of the host name or because of DNS problems. If this happens in the context of a DSF process, it is recommended to review the configuration of the process plugin or contact the process plugin's maintainers in case of the former. DNS problems have a wide variety of sources and usually have to be resolved on the side of the sender.

‎docs/src/s/connection-refused.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
<meta http-equiv="refresh" content="0; url=../operations/troubleshooting/connection-refused" />
2+
<p>If you are not redirected, <a href="../operations/troubleshooting/connection-refused">click here</a>.</p>

‎docs/src/s/connection-timeout.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
<meta http-equiv="refresh" content="0; url=../operations/troubleshooting/connection-timeout" />
2+
<p>If you are not redirected, <a href="../operations/troubleshooting/connection-timeout">click here</a>.</p>

‎docs/src/s/error-http.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
<meta http-equiv="refresh" content="0; url=../operations/troubleshooting/common-http-status-codes" />
2+
<p>If you are not redirected, <a href="../operations/troubleshooting/common-http-status-codes">click here</a>.</p>

‎docs/src/s/error-ssl.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
<meta http-equiv="refresh" content="0; url=../operations/troubleshooting/ssl" />
2+
<p>If you are not redirected, <a href="../operations/troubleshooting/ssl">click here</a>.</p>

0 commit comments

Comments
 (0)