Sage 10 and Bud: 400 error on dev and proxy

bud
1

After installing Sage beta, build works, but dev fails,

I’m confused about dev now. I installed Acorn via composer, and modified the bud.config.js, setting proxy and serve to my urls, but I’m getting error 400 in both cases.

❯ yarn dev
yarn run v1.22.17
$ bud dev
[99%] [done] › MultiCompiler plugins

┌ assets ───────────────────────────────────────────────────┐
│                                                           │
│   name                        cached    hot         size  │
│                                                           │
│   vendor/bud.app.editor.js      ✘        ✘     105.88 kB  │
│                                                           │
│   app.js                        ✘        ✘       24.3 kB  │
│                                                           │
│   editor.js                     ✘        ✘      14.89 kB  │
│                                                           │
│   manifest.json                 ✘        ✘     110 bytes  │
│                                                           │
│   entrypoints.json              ✘        ✘     109 bytes  │
│                                                           │
│   wordpress.json                ✘        ✘      33 bytes  │
│                                                           │
│                                                           │
└───────────────────────────────────────────────────────────┘

◉ 400 [dev] https://localhost:3000
◉ 400 [proxy] https://my-site.local

I am using Local (by Flywheel) with Local’s self-assigned SSL, Apache and PHP 7.4.1 which had no problem with Sage 9.x projects, but the setup is different now for development.

Is this a Me-problem or do I need to configure something more with Local’s setup?

2

I think this is likely due to Bud needing some better SSL support, which should be landing very soon:

Are you able to temporarily disable HTTPS on your local dev site? That issue above also has an example of getting SSL working right now with Bud thanks to @strarsis

3

@ben I just wanted to confirm, that working without SSL on Flywheel Local does work. So, I’ll remain without it for now. Thanks!

2 Likes
4

thanks for your patience @djmtype!