Contents
- Upload files via Customer Portal
- Automatic upload of sos reports during archive creation
- Red Hat Support Tool
- Upload Scripts
- Secure FTP
- Splitting files into parts for upload
- Computing file digests
Upload files via Customer Portal
You can now upload files up to 250GB in size directly to the Customer Portal. There is no longer any need to use a separate mechanism for uploading large files. Refer to Attaching files via Portal UI for attaching files via the Red Hat Customer Portal.
There is a known issue with the IE browser timing out with uploads that take longer than 15 minutes. This should only happen with extremely large uploads. If you need to provide very large files, please use Chrome/Firefox or FTP until a fix is available.
Automatic upload of sos reports during archive creation
As of sos-3.9 and later, sos supports the --upload option to automatically upload an archive once it is generated. Note that a local copy of the archive will still exist.
When run on a Red Hat Enterprise Linux system, using the --upload option will prompt the user for their Customer Portal credentials:
# sos report --upload
sos report (version 4.11.2)
[...]
Please enter the case id that you are generating this report for []: 123456
Setting up archive ...
Setting up plugins ...
[...]
Your sosreport has been generated and saved in:
/var/tmp/sosreport-myhost-123456-2026-06-30-sgczqyo.tar.xz
[...]
Please send this file to your support representative.
Upload target set to Red Hat Upload Target
Attempting upload to Red Hat Customer Portal
Please visit the following URL to authenticate this device: https://sso.redhat.com/device?user_code=USER-CODE
Device authorized correctly. Uploading file to Red Hat Customer Portal
File /var/tmp/sosreport-myhost-123456-2026-06-30-sgczqyo.tar.xz uploaded successfully
Uploaded archive successfully
By providing a case number and authorizing the user which is capable of accessing the specified case number, sos will upload the resulting archive directly to the case upon completion. If either of these are not provided or are incorrect (e.g. an incorrect case number for the credentials provided), then sos will fallback to uploading the archive to Red Hat's secure FTP server, like:
# sos report --upload --batch
sos report (version 4.11.2)
[...]
Your sosreport has been generated and saved in:
/var/tmp/sosreport-myhost-2026-06-29-jovwstl.tar.xz
[...]
Please send this file to your support representative.
Upload target set to Red Hat Upload Target
Attempting upload to Red Hat Secure FTP
Please visit the following URL to authenticate this device: https://sso.redhat.com/device?user_code=NEXT-CODE
Device token authorization has been cancelled by the user.
User nsLxzAnD used for anonymous upload. Please inform your support engineer so they may retrieve the data.
File /var/tmp/sosreport-myhost-2026-06-29-jovwstl.tar.xz uploaded successfully
Uploaded archive successfully
Note: The anonymous user is a temporary user that may not be re-used, and must be provided to your support engineer in the relevant support case so that the engineer will be able to retrieve and review the archive.
Previously, a user could use --upload-user and --upload-pass options (or SOSUPLOADUSER and/or SOSUPLOADPASSWORD environment variables) to provide credentials to upload the sosreport without any user interaction. This option is now deprecated, in favour of device authorization via Customer Portal WebUI. The only non-interactive option is the anonymous upload to SFTP where the user must provide the temporary user to the support engineer.
Note: redhat-support-tool and redhat-support-lib-python have been deprecated in RHEL 8 and will not be shipped in RHEL 9 onwards
See "Red Hat Support Tool (RHST) Deprecation Guide" and "Red Hat Secure FTP - User Guide " which outline equivalent commands that can be used to replace many of the commonly used redhat-support-tool functions.
Note: Red Hat Support tool has overcome the restriction of 1GB for each single file upload in the newer versions of the tool (starting from redhat-support-tool >= 0.13.0) for active minor versions of RHEL 7 and RHEL 8. Now, files greater than 1GB also can be directly uploaded to the case. This has been addressed via RHBZ Bug 1765392 and has been fixed with erratum RHBA-2022:0623.
Note: For RHEL 6, there is still a size restriction of 1GB for each single file uploaded, and the RHEL 6 build will soon stop working. For more details see this solution
-
To Case directly: To upload files directly from your system, you can also use Red Hat Support Tool (redhat-support-tool). It gives you flexibility and also scripting capabilities. The simplest way to upload files, e.g.: sosreport, is this:
$ redhat-support-tool addattachment -c CASE_NUMBER /path/to/sosreport
For large files, you may add the -s option. This may only be needed in case you have a slow bandwidth or your organization's file transfer connections are timed/capped.
Note: See Red Hat Access: Red Hat Support Tool for more complete information on redhat-support-tool, including installation instructions.
Upload Scripts
RHEL 8 deprecated redhat-support-tool. RHEL 9 removed it. Red Hat also removed other upload tools that use basic authentication. See How do I use the CLI to upload support case attachments? for an easy-to-use method to upload support case file attachments, both directly to the Red Hat Customer Portal and via Secure FTP. This solution includes attached scripts to automate file uploads.
Secure FTP
Red Hat’s new Secure FTP platform has been made available: sftp.access.redhat.com
The new platform replaces our legacy dropbox.redhat.com file sharing platform and aims to provide a sustainable, cross-platform, command-line accessible endpoint for customers to upload files to Red Hat. The new Secure FTP can be used to attach files to support cases, as well as simply share files with Red Hat outside of support cases. You can learn more about how to use the new Secure FTP platform in the "Red Hat Secure FTP - User Guide".
Splitting files into parts for upload
While some customers have no problem uploading 50GB vmcore files to Red Hat, others have problems with anything over 1-2GB in size. Sometimes large uploads do not complete reliably either due to file size or network congestion or other issues resulting in failure to complete the upload successfully. Failed uploads often must be resumed from the beginning of the file.
If you have had trouble uploading a file in the past to either the portal or via redhat-support-tool (or FTP) due to size, network stability, or other issues, then the file can be split into parts and each smaller part uploaded. The current recommendation when splitting a large file, such as a vmcore, into parts is to break the file into 1GB chunks as a starting point. If that still fails, fallback to 512m size and try again.
Computing file digests
-
To compute the MD5 message digest of the files you uploaded, run
$ md5sum [filename]
-
Or, alternatively, to compute the SHA1 message digest of the files you uploaded, run
$ sha1sum [filename]
Firewall Configuration
In case you're behind a firewall, you might want to allow access to the following:
Footnotes