Error Messages

Below you can see a list of Stream's common error messages, descriptions and causes, and possible solutions.

Message	Description and Causes	Solutions
Low disk space. Make sure to have at least 100MB of free disk space.	Stream checks the amount of available space on start of each camera process. If there is a shortage, it displays this message and aborts immediately. There could be some rare cases where docker is setup incorrectly and does not have access to all available disk space, mostly with older docker versions.	Free up disk space. Update docker. Move Stream config directory and/or docker app to another disk with more space available.
[STR0008] The URL for the camera in config.ini is incorrect or unavailable. - If it's an RTSP feed, we periodically try to connect in case it comes online. - Make sure the camera URL is correct. You may change it and then start Stream again. - For more info, go to Stream Configuration URL Guide - Press Ctrl-C to exit.	Video source is not reachable. It could be due to network errors, or incorrect network configuration, like firewall or IP filter. Could also just be a spelling error. Stream usually starts trying to reconnect immediately with increasing time intervals, showing its attempts in the log. If subsequent reconnection attempts fail, it indicates there is a network or source issue. Sometimes this happens due to docker bad figuration.	Check if source is reachable from the same machine by opening the url in VLC player. Check docker settings, enable host network mode by adding '--network host' to the docker command. Try pinging the source from within the docker by adding 'docker run ... curl SOURCE_URL' to the usual docker command.
The timezone camera["timezone"] is not valid. Please check your config.ini file.	Most likely cause is incorrect timezone in config.ini file, or incorrect config.ini in general.	Try setting 'timezone = UTC' in config.ini and see if it fixes the issue. If not try deleting the config.ini entirely and letting Stream make a new one.
[STR0003] There are no camera(s) set in the config.ini file. Please add a camera URL and try again. 'For more info, go to Stream Configuration Guide	Incorrect config.ini file.	Add camera section to config.ini according to the docs. Can also delete existing config.ini and let stream make a new one.
[STR0004] This license has expired. Please go here to subscribe.	License issue.	Update license.
[STR0005] The camera registration failed. This can happen when you use a different license key. Go to your Stream folder and remove the files in .stream/	Our server returned 404 error when Stream tried to register user's camera. Must be some license mismatch.	Delete file in STREAM_DIR/.stream or the entire STREAM_DIR.
[STR0006] The Stream license and computer clock are out of sync. Please reset the computer clock time and re-run the Docker command to activate the new camera.	Stream checks with a server what time it is currently for the given timezone and if user's computer has an incorrect time set, displays this message.	Set computer time correctly and run Stream again.
Local system time may be out of sync (offset %s). Verify the machine time and date.	Same as above.	Same as above.
[STR0007] Stream periodically "pings home" to validate the subscription. Please provide Internet connectivity and re-run the Docker command to re-activate Stream.	This message indicates there is no access to our server from user's machine to do a periodic license check. It could be due to network issues or network configuration (Firewall, IP filter, proxy, etc). It could also happen when docker isn't well configured.	Check connectivity by pinging https://api.platerecognizer.com/v1/stream. Could also try pinging from within a docker container by adding 'docker run ... curl SOURCE_URL' to the usual docker command. Reach to network admin or ISP to remove blockers.
[STR0009] Stream failed to register the camera. Please double check the camera URL and then re-run Docker to activate the camera. Refer to our Stream Configuration Guide for more info here	Stream tries to register the camera with our server, but the server returns some inconsistent result, indicating some error.	Check url and rerun.
[STR0011] Dwelling Time is not supported on this Stream license. Please remove the dwell_time=true line from your config.ini. To get Dwelling Time, please go here and subscribe to Vehicle MMC package	Dwell time is only supported on licenses with MMC enabled. This error indicates user's license does not have MMC, but they are trying to use dwell_time in their config.	Buy MMC subscription and rerun Stream. Or remove 'dwell_time = true' from config.ini. Could also delete config.ini and let Stream make a new one.
[STR0010] + some error message	Error while creating CSV, JSON, Webhook or VideoHook Could be due to restricted disk access, low disk space, user privileges, etc.	Troubleshoot by disabling all hooks and enabling them one by one.
[STR0011] Vehicle Make Model Color is not supported on this Stream license. Please remove the mmc=true line from your config.ini. To get Vehicle MMC, please go here to subscribe.	MMC requires a separate subscription. User tried to use mmc = true while it is not enabled for their license.	Buy MMC subscription and rerun Stream. Or remove 'dwell_time = true' from config.ini. Could also delete config.ini and let Stream make a new one.
[STR0032] Stream is running out of RAM + numbers. Stopping...	Memory issue. Could be caused by running too many processes at the same time. Could also be caused by a badly configured swap file.	Update docker and Stream to latest versions. Stop unnecessary processes. Monitor memory usage from an OS tool to check which process consumes more memory than it should. Disable unnecessary Stream features that increase memory consumption: video clips, webhooks, image_format, csv, etc. Reduce the amount of cameras processed by the same machine.
[STR0032] Stream is running out of RAM. Exiting.	Same as above. Previously this error was caused by memory leak in Tensorflow.	Make sure to update Stream to the newest version first.
"[STR0032] Process crashed unexpectedly. RAM usage: X/Y MB. Stopping..."	The Stream was forcefully shutdown. This is either caused by RAM shortage, or a bug.	Check if RAM usage X is close to the amount available Y. If so, try to reduce it as described above. Contact support otherwise.
[STR0013] The --privileged parameter is missing from the Docker command. Please add the --privileged parameter and retry the Docker command. Please refer to our Stream Guide for more info here.	On Jetson device docker needs a --privileged key to run.	Add 'docker run --privileged ...' to docker command.
[STR0014] An Internet connection is required to modify the config.ini file. Please re-establish the Internet connection and then modify the config.ini file. Contact us if you need further assistance here.	Non-perpetual licenses require internet connection every time they change their config. Even for those marked with 'do not ping home'.	Enable internet connection, run Stream, then can disable it again.
[STR0012] The Docker command is incomplete. Make sure it includes LICENSE_KEY. Please refer to our Stream Guide for more info here.	User forgot -e LICENSE_KEY=XXXXX in their docker command.	Add -e LICENSE_KEY=XXXX.
[STR0015] The License Key in the Docker run command cannot be found. Please double-check the License Key and then re-run the Docker command. Contact us if you need further assistance here.	Stream connected to our server, but the latter does not recognize user's license key. Either the key was misspelled or it was removed for some reason.	User should check their license key. Check if user's license key is in the system.
The license could not be retrieved.	This could happen when Stream does not have an internet access and tries to check the license file locally, but the file is missing or corrupted. Could also happen with perpetual licenses when their license file got deleted or corrupted.	Check the file system and STREAM_DIR. Restore internet access and rerun Stream. Remove STREAM_DIR and let stream regenerate the config and license files.
[STR0016] License validation failed. This device hardware does not match the device initially used with this license. Contact us if you need further assistance here.	The license file was created on another device or some hardware changed on this device.	Remove license files in STREAM_DIR/.stream or the entire STREAM_DIR to let Stream generate new license files.
[STR0017] The number of cameras listed in the config.ini exceeds the number of cameras supported for this Stream license. Contact us if you need further assistance here.	User tried to use more cameras in their config than their license allows.	Disable unnecessary cameras with 'active = false' in the config. Buy extra cameras for this license.
[STR0018] To best help us help you, please include the following when you contact us. - Steps to reproduce the behavior. - Screenshot of the error or command output.	Some error happened during initialization phase, which should be displayed before this one. This error message by itself does not bear any information and is only to provide guidance.	NA
Video file format cannot be read or the file is corrupted. Aborting...	User has tried to use file-upload functionality, but the file they are sending to Stream is somehow broken or of unknown format. This could also happen if file was corrupted during network transfer.	Check if this type of file could be read by normal means. Try sending the file again.
[STR0001] This license has ran out of the video process time allocated. The timer will reset on the anniversary of the subscription or free trial. Contact us if you need further assistance here.	User has tried to use file-upload functionality, but their license is out of video processing time.	Wait for license to reset processing time. Buy more video time for this license.
Failed to load detection zone: + name of the mask	User specified mask name to use with Stream, but an attempt to load it from file failed. Most likely cause is unknown image format.	Try running Stream without a mask first. Try using another image format, like .jpg, for a mask.
Filename + is not writable.	Permission error when trying to write file to disk. Could also be caused by another application, like antivirus or Google Drive, locking access to folder. Or by disk space shortage.	Check user rights. Add STREAM_DIR to antivirus/Google Drive exceptions.
[STR0030] The image cannot be saved to disk. Check the filesystem permissions and make sure that it is writable.	Same as above.	Same as above.
Error while sending cached data during init: + error message	Stream is trying to process cached webhooks on init but fails. Could be due to permissions error like above. Stream will continue and try again later.	Same as above.
[Error details`] + error message	Some network issue. Could be ignored if just an off occurrence.	NA
Webhook: Error while caching results to disk. [Error details]: + error message It could be caused by a shortage of disk space or other programs locking access to the cache file. Stream will continue without caching.	Same as above. Most likely cause is another app meddling with STREAM_DIR. Stream will disable cache and continue. Old cached data will stay on disk and Stream will try to send it during next run. New data will not be cached.	Check user rights. Add STREAM_DIR to antivirus/Google Drive exceptions.
[STR0024] The webhook target is not responding or is unreachable. Please check your webhook system and try again. [Error details]: + error message Go here for additional help	Webhook is not responding. Could be due to network issues. If using webhook.site they have a limit on the amount of requests that could be processed.	Solve webhook issue and rerun Stream.
[STR0025] The webhook queue has reached a maximum size of 100 entries. Please optimize your webhook receiving server to process the requests from Stream. Please go here for more info.	Webhook is processing requests slower than Stream is sending them.	Solve webhook issue and rerun Stream.
[STR0021] The file config.ini is invalid. [Error details] + error message	Config contains incorrect values for some parameters. Like 'mmc = 5'.	Check config and try to find the wrong value. Delete STREAM_DIR and let Stream make a new config.
[CODEC @ 0xFFFFFFF] + error message	Video codec error. CODEC could be hevc, rtsp, rtmp, etc. Most video codecs encode one frame on top of another, which means if one frame gets lost in transit or corrupted, it affects several frames down the line. This error could be caused by network connectivity issues between the camera and Stream machine. It could also be caused by camera device being overloaded and outputting jumbled frames, or by Stream machine being overloaded and losing incoming frames. The latter is usually indicated by low Health Score in Stream's logs. Those errors are harmless most of the time and action should only be taken if they are frequent and affect service quality.	Decrease output camera resolution or fps. Reduce the load on camera device by turning off unused video streams or processes. Switch to another video codec in camera's settings. Switch to more reliable TCP-based video protocol. Decrease the load on Stream machine (reduce the number of cameras, increase sample parameter, turn saving videos, images, csv, json off if not used, etc). Reduce network congestion by turning high traffic services off or moving them.
Other cryptic error messages.	Internal error. Could be caused by wrong docker image, wrong docker command or a bug.	Check if docker image matches the platform. Check if docker command is correct. Contact dev team if it seems like a bug.
Error grabbing logs: invalid character '\x00' looking for beginning of value	This issue is related to Docker and indicates that a file in the log driver's storage for the container has become corrupted. This can occur due to an unclean shutdown or if the host ran out of space.	As this only occurs on some Docker Desktop versions, upgrading to the latest version is advisable. The error could be easily resolved by cleaning up or deleting the corrupted log file and then restarting the container. Additionally, you can run the container with JSON logging driver flags, which offer options for log rotation and recycling. More details about the available options can be found here.
Check docker command. Problem with accessing resources: + case specific error message	Stream cannot access GPU/NPU/DLPU device. Relevant for gpu, jetson, arm, raspberry-pi docker images. This might be caused by incomplete docker command, or wrong user permissions (e.g. missing proper --runtime nvidia, --privileged, --user ..., --group-add ..., -v ... flags).	Check docker command. Check if docker user has access to the hardware accelerator device. Troubleshoot by running as root.