Airtable Attachment Upload Error - Seeking Help to Diagnose

[FilipZarzycki]

Hello everyone,

I’m encountering a frustrating issue with Airtable on my company’s PCs, and I’m hoping someone here can help me diagnose it.

• Account & Plan: I'm using the same Airtable Pro account across all devices.
• PC 1 (Main): On my main PC, which runs Windows 11, I can upload files to Airtable without any issues. This includes all accepted file formats ranging from a few kilobytes to over 10MB.
• PC 2 & 3 (Company PCs): However, on two other company PCs running Windows 10, I'm experiencing constant upload errors. These PCs have Microsoft Defender turned off and no antivirus installed.
• Tried Solutions:
  • I’ve tried using both the standalone Airtable app and various web browsers, but the error persists across all attempts.
  • I’ve cleared the browser cache and checked for any Chrome extensions that might interfere, but found nothing unusual.
• Other Notes: The main difference I’ve noticed is the operating system—Windows 11 on the PC where it works, and Windows 10 on the ones where it doesn’t.

I’m out of ideas at this point. Has anyone else encountered a similar issue or have any suggestions on what might be causing this? Any help would be greatly appreciated!

[edit]

I checked the web browser console during the upload and it yelds this error. It seems that there is potential issue with SSL certificate. Ideas? 

PUT https://s3.dualstack.us-east-1.amazonaws.com/dl.getforma.com/.directUploadAttachment/cf6a78f491d2049... net::ERR_CERT_COMMON_NAME_INVALID
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
uploadPartBytes @ client_file_uploader-BN7BIMWF.js:4
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
hm @ client_file_uploader-BN7BIMWF.js:4
run @ client_file_uploader-BN7BIMWF.js:4
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
uploadChunk @ client_file_uploader-BN7BIMWF.js:4
await in uploadChunk
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
uploadFile @ client_file_uploader-BN7BIMWF.js:4
await in uploadFile
_m @ client_file_uploader-BN7BIMWF.js:4
start @ client_file_uploader-BN7BIMWF.js:4
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
Tm @ client_file_uploader-BN7BIMWF.js:4
(anonymous) @ client_file_uploader-BN7BIMWF.js:4
value @ client_file_uploader-BN7BIMWF.js:4
fg @ client_file_uploader-BN7BIMWF.js:9
await in fg
(anonymous) @ client_file_uploader-BN7BIMWF.js:9
Promise.then
upload @ client_file_uploader-BN7BIMWF.js:9
Ci.startUpload @ client_file_uploader-BN7BIMWF.js:11
Od @ client_file_uploader-BN7BIMWF.js:9
client_file_uploader-BN7BIMWF.js:4

Thank you!

[Jeri_Vespoli]

The error you're seeing (net::ERR_CERT_COMMON_NAME_INVALID) typically points to an SSL certificate mismatch, which can happen when the certificate being presented by the server does not match the domain name you're accessing. Here are a few potential solutions to troubleshoot and resolve this issue:

1. Check System Date and Time:

   • Ensure that the date and time settings on the Windows 10 PCs are correct. An incorrect date or time can cause SSL certificate issues.

2. Check Network Settings:

   • Verify if the network settings on the Windows 10 PCs are different from those on the Windows 11 PC. This includes checking any proxy settings, VPN connections, or specific DNS settings that might interfere with the SSL handshake.

3. Update Root Certificates:

   • Ensure that the Windows 10 PCs have the latest root certificates installed. Windows updates often include updates to the root certificates. Running Windows Update could help if the PCs are behind on updates.

4. Clear SSL State:

   • Clear the SSL state in the internet options. You can do this by:
     • Going to Control Panel > Internet Options > Content tab > Clear SSL State.

5. Test with Another Network:

   • Try connecting the Windows 10 PCs to a different network, such as a mobile hotspot, to see if the issue is related to the current network.

6. Browser-Specific Issues:

   • Try accessing Airtable in an incognito window or another browser to see if the issue persists.
   • Disable any browser extensions that might interfere with SSL connections.

7. Check for Intermediate Certificate Issues:

   • If possible, inspect the SSL certificate chain on the failing PCs using tools like SSL Labs' SSL Test or a browser's developer tools under the security tab. This can help identify if an intermediate certificate is missing or not being trusted.