Cloudflare Developers•4mo ago

"No wrangler.toml found."

I never had this issue before? And we've been working with Pages for years now lol. - deployment ID (which is actually failing now, for some reason too): be6324d8-bd03-474d-8388-e50006fb7e0e

15 Replies

Chinoman10•4mo ago

For some additional context, this is on one of our oldest projects, which (unfortunately) still use Jekyll and not Astro. But you can see the root directory is /, which is where wrangler.toml is at.

Vero•4mo ago

Hey, I've just escalated your issue. A support engineer will look into it when they're available

Walshy•4mo ago

was this ever working with your wrangler.toml? your last success also did not have a wrangler.toml but succeeded looks like the ruby version you're trying to use changed which caused the failure - not related to wrangler.toml

Chinoman10•4mo ago

I changed to build v2 and now it detects automatically... I wasn't even aware of this "v2" and it was announced last year already! And I'm super stoked the env includes bun ! Much faster builds than using npm 😅

Chinoman10•4mo ago

yes yes I realized that, which is why I changed it to 2.7.1... that's how I found out about the v2 build environment. Doing one last (hopefully) push/deployment... let's see how it goes... it usually takes ~10m to build... hopefully now it'll go down to ~5-6... Well sh1t... deployment 2a6edeea-101b-45d8-be3a-ba66db216dca failed.

13:02:18.556    ffi-1.17.0-x86_64-linux-musl requires rubygems version >= 3.3.22, which is
13:02:18.557    incompatible with the current version, 3.1.2
13:02:18.593    Error: Exit with error code: 5

13:02:18.556    ffi-1.17.0-x86_64-linux-musl requires rubygems version >= 3.3.22, which is
13:02:18.557    incompatible with the current version, 3.1.2
13:02:18.593    Error: Exit with error code: 5

Last time this happened because of the RUBY_VERSION being 2.7.5 instead of 2.7.1... but even though it's now set to 2.7.1 ... it still doesn't work. hmm I think I found the issue... 'liquid' version needs to be forced to 4.0.4 when using ruby 2.7.1... and apparently there's no fix (at least a few months ago when I ran into this). Triggered a redeployment now with the forced version... edit: didn't work.

Chinoman10•4mo ago

I can't even rollback 😭 (redeploy an older (working) version)

Chinoman10•4mo ago

Clearly something's broken with the 'v2' build system. 72a6c5f9-e828-47bd-ac19-bf7d6967f718 this deployed successfully, already using ruby 2.7.1, liquid 4.0.4 :shrugg: I'm temporarily moving back to v1 so I can make this deployment... but I'll change it back to v2 afterwards, and I'd like to get it to work. Any ideas are welcome... wrangler.toml is still not found in v1, and when I upgrade to v2 it doesn't work, despite having forced specific (working) ruby versions, etc.

Walshy•4mo ago

wrangler.toml isn't supported in v1

Chinoman10•4mo ago

Ha! Didn't expect that lol Well, let's focus on getting v2 to work then 😬

Walshy•4mo ago

what's the latest deploy id for v2?

Chinoman10•4mo ago

https://dash.cloudflare.com/b49cf04faa95acedabf98a027abb56cf/pages/view/client-caoba-hotels/acd423bf-93ad-4ada-b2f0-17d4622e2f8a

acd423bf-93ad-4ada-b2f0-17d4622e2f8a - here's the ID; but I left the URL in case you want to check the account too 👍

Walshy•4mo ago

ffi-1.17.0-x86_64-linux-musl requires rubygems version >= 3.3.22, which is
incompatible with the current version, 3.1.6

ffi-1.17.0-x86_64-linux-musl requires rubygems version >= 3.3.22, which is
incompatible with the current version, 3.1.6

have you tried 3.3.22?

Chinoman10•4mo ago

I don't define the 3.1.6 version anywhere.

Walshy•4mo ago

you must do somewhere, default is 3.2.2 https://developers.cloudflare.com/pages/configuration/language-support-and-tools/#v2-build-system

Chinoman10•4mo ago

Here's the Gemfile 😅

source 'https://rubygems.org'

gem 'bundler'
gem "liquid", "~> 4.0.4"
gem 'jekyll', github: "jekyll/jekyll"

group :jekyll_plugins do
    gem 'jekyll-watch'
    gem 'jekyll-sitemap'
    gem 'jekyll-seo-tag'
    gem 'jekyll-multiple-languages-plugin'
    gem "jekyll-sass-converter", "~> 2.0"
end

gem 'wdm', '~> 0.1.1', :install_if => Gem.win_platform?

gem "webrick", "~> 1.7"

source 'https://rubygems.org'

gem 'bundler'
gem "liquid", "~> 4.0.4"
gem 'jekyll', github: "jekyll/jekyll"

group :jekyll_plugins do
    gem 'jekyll-watch'
    gem 'jekyll-sitemap'
    gem 'jekyll-seo-tag'
    gem 'jekyll-multiple-languages-plugin'
    gem "jekyll-sass-converter", "~> 2.0"
end

gem 'wdm', '~> 0.1.1', :install_if => Gem.win_platform?

gem "webrick", "~> 1.7"

the 'webrick' and 'liquid' were ones I added today, to try and fix it. I remember I had to force liquid to be 4.0.4 for another jekyll project also deployed to pages. I found this support article you also replied to @walshydev: https://community.cloudflare.com/t/deployment-failing-rubygems-version/446483 But as you can see, we already tried the sass-converter change 😂

Gaming

Programming

"No wrangler.toml found."