- 
                Notifications
    
You must be signed in to change notification settings  - Fork 10.3k
 
Description
Preliminary Checks
- This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
 - This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
 
Description
Hi everyone,
We've recently migrated our WordPress backend (used as a headless CMS) from InMotion Hosting to WP Engine. Our frontend is built with Gatsby. After updating the API endpoint to point to the new WP Engine server, we're now encountering the following error during build or development:
RequestError: 382F0000:error:0A000119:SSL routines:ssl3_get_record:decryption failed or bad record
mac:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:623:
Reproduction Link
i cant upload the link , because this is for company
Steps to Reproduce
1.Set up a Gatsby site using gatsby-source-wordpress to pull data from a WordPress backend.
2.Initially connect to a WordPress site hosted on InMotion – build and development work as expected.
3.Migrate the WordPress site to WP Engine.
4.Update the API endpoint in the Gatsby config to point to the new non-SSL (http://) WP Engine WordPress site.
5.Run gatsby develop or gatsby build.
6.Observe the build process fail with the following SSL error:
RequestError: 382F0000:error:0A000119:SSL routines:ssl3_get_record:decryption failed or bad record
mac:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:623:
Expected Result
Gatsby should successfully fetch data from the new WordPress backend hosted on WP Engine (using the configured non-SSL http:// API endpoint) and complete the build process without any errors.
Actual Result
When running gatsby develop or gatsby build, the process fails with the following SSL error, even though the API endpoint is set to http:// (non-SSL):
RequestError: 382F0000:error:0A000119:SSL routines:ssl3_get_record:decryption failed or bad record
mac:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:623:
Environment
System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (131.0.2903.112)
  npmPackages:
    gatsby: ^5.13.7 => 5.14.5
    gatsby-plugin-anchor-links: ^1.2.1 => 1.2.1
    gatsby-plugin-fastify: ^0.13.4 => 0.13.4
    gatsby-plugin-image: ^3.13.1 => 3.14.0
    gatsby-plugin-manifest: ^5.13.1 => 5.14.0
    gatsby-plugin-postcss: ^6.13.1 => 6.14.0
    gatsby-plugin-recaptcha: ^1.0.5 => 1.0.5
    gatsby-plugin-sharp: ^5.13.1 => 5.14.0
    gatsby-source-gravityforms: ^1.0.18 => 1.0.18
    gatsby-source-wordpress: ^7.13.4 => 7.15.0
    gatsby-transformer-sharp: ^5.13.1 => 5.14.0
  npmGlobalPackages:
    gatsby-cli: 5.14.0Config Flags
No response