#vite

BestCodes Love this. I am too obsessed with clicking that copy button just to hear the success noise

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Amy Egan Did you try the debugging tips linked above? I'd recommend checking the build settings and output to figure out why the page is missing

Pauline P. Narvas Hi, @azziefuzzie! Welcome to the Vercel Community. It looks like the issue comes from how Eleventy and Vite are handling their output directories. Right now, you have a mismatch: * Eleventy outputs to `_site` * Vite outputs to `.11ty-vite` This conflict prevents Vercel from picking up the correct build output. Try updating your Eleventy config so that Vite builds to the same directory as Eleventy: ```js _eleventyConfig_.addPlugin(EleventyVitePlugin, { tempFolderName: tempFolder, viteOptions: { root: "src", publicDir: "public", build: { outDir: path.resolve(process.cwd(), "_site"), // Match Eleventy output emptyOutDir: false, // Prevents Eleventy files from being deleted rollupOptions: { input: {}, }, }, }, }); ``` If that doesn't work, try removing the custom `outDir` from your config and let `EleventyVitePlugin` handle it automatically.

Azziefuzzie Thanks, @pawlean I tried both solutions also tried removing the with removing the “outDir: path.resolve(process.cwd(), '\_site')”, couldn’t get it to work though still the same error : import path from 'path'; import fs from 'fs'; import htmlmin from 'html-minifier'; import EleventyVitePlugin from '@11ty/eleventy-plugin-vite'; import pluginPug from '@11ty/eleventy-plugin-pug'; export default function (*eleventyConfig*) { // --- Ensure temp folder exists --- const tempFolder = '.11ty-vite'; if (!*fs*.existsSync(tempFolder)) *fs*.mkdirSync(tempFolder, { recursive: true }); // --- Server --- *eleventyConfig*.setServerOptions({ port: 3000 }); // --- Plugins --- *eleventyConfig*.addPlugin(pluginPug); *eleventyConfig*.addPlugin(EleventyVitePlugin, { tempFolderName: tempFolder, viteOptions: { root: 'src', publicDir: 'public', build: { outDir: path.resolve(process.cwd(), '\_site'), emptyOutDir: false, rollupOptions: { input: {}, }, }, css: { preprocessorOptions: { scss: { additionalData: \`@import "@styles/utils/variables.scss";\`, }, }, }, resolve: { alias: { '@styles': path.resolve(process.cwd(), 'src/styles'), '@app': path.resolve(process.cwd(), 'src/app'), '@utils': path.resolve(process.cwd(), 'src/app/utils'), '@components': path.resolve(process.cwd(), 'src/app/components'), '@shaders': path.resolve(process.cwd(), 'src/app/shaders'), '@classes': path.resolve(process.cwd(), 'src/app/classes'), '@animations': path.resolve(process.cwd(), 'src/app/animations'), '@pages': path.resolve(process.cwd(), 'src/app/pages'), }, }, }, }); // --- Passthrough copy --- *eleventyConfig*.addPassthroughCopy('public'); *eleventyConfig*.addPassthroughCopy('src/app'); *eleventyConfig*.addPassthroughCopy('src/fonts'); *eleventyConfig*.addPassthroughCopy('src/styles'); *eleventyConfig*.setServerPassthroughCopyBehavior('copy'); // --- HTML minify --- *eleventyConfig*.addTransform('htmlmin', (*content*, *outputPath*) => { if (*outputPath* && *outputPath*.endsWith('.html')) { return htmlmin.minify(*content*, { useShortDoctype: true, removeComments: true, collapseWhitespace: true, }); } return *content*; }); // --- Return directory config --- return { dir: { input: 'src/views/', output: '\_site', includes: '\_includes', data: '\_data', }, passthroughFileCopy: true, htmlTemplateEngine: 'pug', }; };

system Hi @azziefuzzie! 🔔 This thread's been quiet for a while. If you're still facing issues, please share any relevant details (logs, screenshots, error messages) so we can take another look!

Ryu Hi JorgY\_, Given your diagnostic output, I’d focus on the Supabase connection type rather than the PHP env vars. The suspicious part is: ``` Database: Supabase Postgres Direct connection Port: 5432 pdo_pgsql_loaded: true sslmode=require Works locally, fails on Vercel ``` Supabase direct database connections use IPv6 unless you have the IPv4 add-on enabled. Vercel serverless functions are commonly the case where the direct `db.<project-ref>.supabase.co:5432` connection fails, even though the same credentials work locally. I’d switch the deployed PHP API to the Supabase **Shared Pooler / Supavisor** connection string instead of the direct connection string. In Supabase: ``` Project → Connect → Connection string → Pooler ``` For serverless functions, try the transaction pooler first: ``` host: aws-<region>.pooler.supabase.com port: 6543 user: postgres.<project-ref> database: postgres sslmode: require ``` So your PDO DSN would be shaped more like: ``` $dsn = "pgsql:host={$host};port=6543;dbname={$database};sslmode=require"; $pdo = new PDO($dsn, $username, $password, [ PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION, ]); ``` Make sure the username changes too. For the pooler it is usually `postgres.<project-ref>`, not just `postgres`. Supabase explains the IPv4/IPv6 difference here: https://supabase.com/docs/guides/troubleshooting/supabase--your-network-ipv4-and-ipv6-compatibility-cHe3BP One more thing: temporarily log the real PDO exception message, but not the password or full connection string. The difference between `connection refused`, `timeout`, and `password authentication failed` will confirm whether this is network/IPv6 or credentials.

Pauline P. Narvas Welcome to the Vercel Community! Cool project Vercel’s CDN supports HTTP/2 through ALPN negotiation. When testing with curl, try: `curl -I --http2-prior-knowledge https://reeflocal.io` The results are: ``` HTTP/2 200 accept-ranges: bytes access-control-allow-origin: * age: 69 cache-control: public, max-age=0, must-revalidate content-disposition: inline content-type: text/html; charset=utf-8 date: Fri, 17 Apr 2026 11:08:08 GMT etag: "4b264812b229d2b3a2943254c19261d8" last-modified: Fri, 17 Apr 2026 11:06:58 GMT server: Vercel strict-transport-security: max-age=63072000 x-vercel-cache: HIT x-vercel-id: lhr1::29hdk-1776424087993-d123805054ce content-length: 9145 ``` For Brotli/gzip compression, include the Accept-Encoding header: `curl -H "Accept-Encoding: gzip, br" -I https://reeflocal.io` I can see: ``` HTTP/2 200 access-control-allow-origin: * age: 108 cache-control: public, max-age=0, must-revalidate content-disposition: inline content-encoding: br content-type: text/html; charset=utf-8 date: Fri, 17 Apr 2026 11:08:46 GMT etag: W/"4b264812b229d2b3a2943254c19261d8" last-modified: Fri, 17 Apr 2026 11:06:58 GMT server: Vercel strict-transport-security: max-age=63072000 x-vercel-cache: HIT x-vercel-id: lhr1::f8fq6-1776424126886-571b3cb5b9a5 ``` If you’re behind a proxy, it might downgrade connections to HTTP/1.1. Test from a different network to confirm!