This page explains the network requirements for Digiexam after it has been installed.
End-user network requirements for Digiexam are low, the test site must allow outbound traffic via HTTPS (port 443) and typical bandwidth usage is about 3Kb download per student for the exam start and 2Kbit/s upload during the exam session.
One thing to keep in consideration that is not directly related to Digiexam is that the WiFi hotspot used during the exam must be scaled to handle connections from all the students that write the exam.
Ports
Ports required are:
- 80 (HTTP, TCP outbound)
Used for redirect to HTTPS when the end-user enters the address in the browser. No other traffic is allowed over HTTP. - 443 (HTTPS, TCP outbound)
All traffic between the end-user and the service is sent over this port.
Hosts
Traffic to the following hosts must be allowed on the ports mentioned above.
- https://cdn.crabnebula.app/download/digiexam/digiexam/latest/platform/wix-x86_64 (Windows x86_64 download source)
- https://cdn.crabnebula.app/download/digiexam/digiexam/latest/platform/wix-aarch64 (Windows ARM download source)
EU server-specific URLs
- http://www.digiexam.se
- http://www.digiexam.com
- http://app.digiexam.com
- https://spellchecker.digiexam.com
- http://digiexam-live.appspot.com
- http://storage.googleapis.com
- https://event.api.eu.digiexam.com
- https://assignment.api.eu.digiexam.com
- https://lockdown.api.eu.digiexam.com
US server-specific URLs (Only for US customers)
- http://www.digiexam.com
- https://spellchecker.digiexam.com
- http://storage.googleapis.com
- http://app-us.digiexam.com
- http://digiexam-live-us.appspot.com
- https://event.api.us.digiexam.com/
- https://assignment.api.us.digiexam.com/
- https://lockdown.api.us.digiexam.com/
Remote proctoring - Traffic to the following hosts must be allowed on the ports mentioned above.
Downstream
Downstream is mainly used when starting an exam, during the exam, and on hand in only acknowledgments are sent from the server to the client.
Typical payload size:
| Payload type | Size upstream (request) | Size downstream (response) |
|---|---|---|
| List exams (2 exams) | ~300b | ~600B |
| Get exam info (Demo exam, text only) | ~300b | ~600B |
| Download the full exam at the start (Demo exam, text only) | ~300b | ~2KB |
A typical exam start requires 1KB upload and 3KB download per student.
Upstream
Upstream is mainly used to upload answers from the client to the server while the student is writing and at the final hand in.
Statistics from the API:
|
Payload type |
Size upstream (request) |
Size downstream (response) |
|---|---|---|
|
Answer upload (50th percentile) |
2.634KB |
~300b |
|
Answer upload (75th percentile) |
4.711KB |
~300b |
|
Answer upload (90th percentile) |
7.527KB |
~300b |
|
Answer upload (95th percentile) |
10.388KB |
~300b |
|
Answer upload (99th percentile) |
21.817KB |
~300b |
|
Answer upload (100th percentile) |
409.9174KB |
~300b |
Number of uploads per minute: 2
Upstream bandwidth usage per second and student (90th %): 7527 byte * 8 bit/byte * 2 uploads/min / 60 = 1.96Kbit/s
Note: If you are the account manager for your Digiexam environment you should also ensure that any and all external tools (e.g. Geogebra, JSTOR) or media links (YouTube links, course links) that your staff or students will use during any exams should also be whitelisted. If you are uncertain about what might need to be whitelisted, please contact support@digiexam.com for assistance.
Troubleshooting and Network Configuration Check at the Organization Level
Please confirm that native gRPC over HTTPS is allowed to our domains: https://event.api.eu.digiexam.com, https://assignment.api.eu.digiexam.com, https://lockdown.api.eu.digiexam.com, https://event.api.us.digiexam.com, https://assignment.api.us.digiexam.com, https://lockdown.api.us.digiexam.com.
By preserving ALPN “h2” and permitting TLS 1.2/1.3 over TCP 443. If SSL inspection is enabled, either bypass it for these hosts or configure the proxy to present a full chain and to avoid downgrading traffic to HTTP/1.1.Please allow AIA/OCSP lookups for Let’s Encrypt so that intermediate certificates and revocation information can be fetched and cached; the common endpoints are under *.lencr.org.
Also ensure client time is correct via NTP, as clock skew can break TLS validation.If an authenticated proxy is required, please ensure a machine-level proxy is in place before user logon, or exempt our domains so devices can reach us pre-session.
Where applicable, verify pre-logon connectivity (Wi-Fi/802.1X, DNS reachability) so devices can contact our services at startup.For quick verification on an affected laptop, please check that HTTP/2 is negotiated and gRPC handshakes succeed by running: curl.exe -vk --http2 https://assignment.api.eu.digiexam.com/ and confirming it reports ALPN, server accepted to use h2 and HTTP/2; then grpcurl -vv assignment.api.eu.digiexam.com:443 and confirming it shows ALPN: h2 and completes; finally, confirm reachability and proxy settings with Test-NetConnection assignment.api.eu.digiexam.com -Port 443 and netsh winhttp show proxy and share the outputs if any step fails.
Kommentarer