---
type: source
title: GrypsTube FAQ
tags: [video-service, faq, troubleshooting]
related: [grypstube, ums, opencast-studio, moodle, typo3-backend]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_grypstube_faq.md"]
---

# GrypsTube FAQ

This source provides a comprehensive list of frequently asked questions and troubleshooting guidance for **GrypsTube**, the central/internal video service at the Universität Greifswald.

## Key Technical Specifications
- **Upload Limit**: Hard limit / maximum of 8GB per file.
- **Session Timeout**: 20 minutes. Uploads exceeding this duration may be aborted.
- **Browser Compatibility**: 
    - Microsoft Edge version 81 or higher is required for playback.
    - Microsoft Edge versions prior to v81 are incompatible.
    - Modern browsers are required.

## Access Control
- **Viewing**: Publicly accessible without an account.
- **Uploading**: Requires a university account with a specific **Serviceflag** in the central identity management system. This flag can be requested via [[ums]].

## Operational Workflow
The process of making a video available follows these stages:
1. **Upload**: The raw file is sent to the server.
2. **Publishing**: Defined as the successful upload of a video combined with the selection of visibility settings (e.g., public or private) and channel assignment.
3. **Transcoding**: The server converts raw uploads into multiple resolutions to optimize playback based on user bandwidth. This is processed in a First-In-First-Out (FIFO) queue, which can lead to several hours of delay during peak times.

## Organization
- **Channels (Kanäle)**: Thematic groupings for videos. Only public videos are visible in channels; private videos (including those with private links) are excluded.

## Troubleshooting and Common Errors
- **"Unknown Error"**: Often a false positive or misleading UI message where the upload continues in the background. Users should keep the browser window open and check for notifications.
- **"Server error. Please retry later"**: 
    - Typically occurs when files lack necessary runtime metadata and require post-processing.
    - Specifically occurs frequently with files from [[opencast-studio]] (MP4/WEBM) because they lack essential runtime metadata.
- **Embedding Issues**: Videos embedded via `<iframe>` in [[moodle]] or [[typo3-backend]] may fail to play. 
    - **Workaround**: The viewer must manually change the video quality from "auto" to a specific resolution.
    - **Alternative**: Use a direct external link to the video.