Next.js build in GitHub Actions fails due to failed Google Fonts fetching #76473

Repk1ns · 2025-02-25T07:32:45Z

Repk1ns
Feb 25, 2025

Summary

I'm experiencing an issue when building my Next.js project in GitHub Actions. The build process gets stuck for several minutes while trying to fetch Google Fonts, and sometimes it fails completely. Here is the relevant error log:

#12 10.13    Creating an optimized production build ...
#12 52.98 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1CzjvWyNPYZvg7UI.woff2 failed, reason: 
#12 52.98 
#12 52.98 Retrying 1/3...
#12 52.99 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1CzjtGyNPYZvg7UI.woff2 failed, reason: 
#12 52.99 
#12 52.99 Retrying 1/3...
#12 52.99 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1CzjvGyNPYZvg7UI.woff2 failed, reason: 
#12 52.99 
#12 52.99 Retrying 1/3...
#12 53.00 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1Czjs2yNPYZvg7UI.woff2 failed, reason: 
#12 53.00 
#12 53.00 Retrying 1/3...
#12 53.01 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1CzjvmyNPYZvg7UI.woff2 failed, reason: 
#12 53.01 
#12 53.01 Retrying 1/3...
#12 53.01 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCv6KVjbNBYlgoC1CzjsGyNPYZvgw.woff2 failed, reason: 
#12 53.01 
#12 53.01 Retrying 1/3...
#12 53.02 request to https://fonts.gstatic.com/s/ubuntu/v20/4iCs6KVjbNBYlgoKew72nU6AF7xm.woff2 failed, reason: 
.
.
.

It retries multiple times, and in some cases, it succeeds after ~7 minutes. However, occasionally, the build fails entirely because it cannot fetch the fonts.

This is how I import the fonts in my Next.js project:

import "../styles/globals.css";
import "../styles/Main.scss";
import Head from "./head";
import NextAuthSessionProvider from "./SessionProvider";
import { Oswald, Ubuntu, Play } from 'next/font/google';

const oswald = Oswald({ subsets: ['latin'] });
const ubuntu = Ubuntu({ weight: ['300', '400', '500', '700'], subsets: ['latin'] });
const play = Play({ weight: ['400', '700'], subsets: ['latin'] });

export default function RootLayout({ children }) {
  return (
    <html lang="en" className={`${oswald.className} ${ubuntu.className} ${play.className}`}>
      <Head />
      <body>
        <NextAuthSessionProvider>
          {children}
        </NextAuthSessionProvider>
      </body>
    </html>
  );
}

Running the build locally works fine. Any ideas on how to shorten the build time and fix this error?

Additional information

No response

Example

No response

icyJoseph · 2025-02-25T08:01:29Z

icyJoseph
Feb 25, 2025
Maintainer

I think, in Github Actions you can highlight the text and try to read what the reason for the error was?

In any case, I could speculate that this is a networking issue. Not sure how to proceed if that's the case though.

What Node.js version does your build action use? I hope it is not some TLS, or IPv6 issue...

4 replies

Repk1ns Feb 25, 2025
Author

unfortunately no, no reason is written here.

I use node20-alpine in my Dockerfile.

icyJoseph Feb 25, 2025
Maintainer

🤔 Could you try with the regular node20 image? I mean, we are in the dark right now, might as well just try.

Repk1ns Feb 27, 2025
Author

Node 20 (without Alpine) works. The build time is still around 21 minutes (quite too much), but there are no font fetch errors. Then I switched to the 22-alpine version, and the font errors came back. The build time with 22-alpine was only 15 seconds faster, so fetching fonts probably aren't a significant factor in build time optimization.

icyJoseph Feb 27, 2025
Maintainer

Wait, so we are narrowing down on the Alpine and other smaller images, right?

There must be a system dependency that's not up-to-date 🤔 TLS, IPv6 still could be culprits, but how to debug any further

Raymond-Ly · 2025-02-25T22:36:55Z

Raymond-Ly
Feb 25, 2025

An alternative is to self host the fonts to avoid network requests.

Download the required font files from Google Fonts.
Store them in your project's public/fonts folder.
Define a global CSS rule to load the fonts.

https://nextjs.org/docs/app/getting-started/images-and-fonts

1 reply

icyJoseph Feb 25, 2025
Maintainer

Right, assuming OP thinks it is acceptable to self host three fonts, etc. But still, what's failing on that GitHub action.... Puzzling 🤔

hashilfinstreet · 2025-10-20T07:18:01Z

hashilfinstreet
Oct 20, 2025

I am also facing this issue. any fix?

0 replies

hashilfinstreet · 2025-10-20T07:27:58Z

hashilfinstreet
Oct 20, 2025

▲ Next.js 14.2.7

Environments: .env

Creating an optimized production build ...
request to https://fonts.googleapis.com/css2?family=Nunito:[email protected]&display=swap failed, reason:

Retrying 1/3...
request to https://fonts.googleapis.com/css2?family=Nunito:[email protected]&display=swap failed, reason:

Retrying 2/3...
request to https://fonts.googleapis.com/css2?family=Nunito:[email protected]&display=swap failed, reason:

Retrying 3/3...
FetchError: request to https://fonts.googleapis.com/css2?family=Nunito:[email protected]&display=swap failed, reason:
at ClientRequest. (/node_modules/next/dist/compiled/node-fetch/index.js:1:66160)
at ClientRequest.emit (node:events:524:28)
at emitErrorEvent (node:_http_client:101:11)
at TLSSocket.socketErrorListener (node:_http_client:504:5)
at TLSSocket.emit (node:events:524:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
at runNextTicks (node:internal/process/task_queues:64:3)
at process.processTimers (node:internal/timers:516:9) ***
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'

Failed to compile.

src/app/fonts.ts
next/font error:
Failed to fetch Nunito from Google Fonts.

Build failed because of webpack errors
The command '/bin/sh -c npm i && npm run build' returned a non-zero code: 1

Error: Process completed with exit code 1.

12 replies

hashilfinstreet Oct 21, 2025

node version is 20

icyJoseph Oct 21, 2025
Maintainer

I was looking at the code that fetches the fonts, and it had been using node_fetch, but now uses the node http client.

For your version it uses node_fetch. Anyway, across versions this is used, even today:

https://github.com/vercel/next.js/blob/v14.2.7/packages/font/src/google/get-proxy-agent.ts

const httpsProxy = process.env['https_proxy'] || process.env['HTTPS_PROXY']

I wonder if this is a thing in GitHub actions that might be slowing things down?

hashilfinstreet Oct 21, 2025

after some retry some time build is passed,

icyJoseph Oct 21, 2025
Maintainer

Yeah, the timeout must be at play right? I wonder if its proxying and that causes the it to be slow... 🤔

hashilfinstreet Oct 21, 2025

hmm,

Moranilt · 2025-12-02T09:45:10Z

Moranilt
Dec 2, 2025

I'm facing the same problem in gilab CI/CD using nextjs v15.5.6. Very long timeout and then exit code.

0 replies

Next.js build in GitHub Actions fails due to failed Google Fonts fetching #76473

Uh oh!

Summary

Additional information

Example

Replies: 5 comments · 17 replies

Uh oh!

icyJoseph Feb 25, 2025 Maintainer

Uh oh!

Repk1ns Feb 25, 2025 Author

Uh oh!

icyJoseph Feb 25, 2025 Maintainer

Uh oh!

Repk1ns Feb 27, 2025 Author

Uh oh!

icyJoseph Feb 27, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

icyJoseph Feb 25, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

icyJoseph Oct 21, 2025 Maintainer

Uh oh!

Uh oh!

icyJoseph Oct 21, 2025 Maintainer

Uh oh!

Uh oh!

Replies: 5 comments 17 replies

icyJoseph
Feb 25, 2025
Maintainer

Repk1ns Feb 25, 2025
Author

icyJoseph Feb 25, 2025
Maintainer

Repk1ns Feb 27, 2025
Author

icyJoseph Feb 27, 2025
Maintainer

icyJoseph Feb 25, 2025
Maintainer

icyJoseph Oct 21, 2025
Maintainer

icyJoseph Oct 21, 2025
Maintainer