# Sage 10 and Bud: 400 error on dev and proxy

**URL:** https://discourse.roots.io/t/sage-10-and-bud-400-error-on-dev-and-proxy/22385
**Category:** bud
**Tags:** sage10
**Created:** 2022-02-23T16:36:57Z
**Posts:** 4

## Post 1 by @djmtype — 2022-02-23T16:36:57Z

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?

---

## Post 2 by @ben — 2022-02-23T17:03:50Z

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

> <https://github.com/roots/bud/issues/934>
>
> ### Terms
> 
> - [X] I have read the [guidelines for Contributing to Roots Projects]…(https://github.com/roots/.github/blob/master/CONTRIBUTING.md)
> - [X] This request is not a duplicate of an existing issue
> - [X] This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots.io/) community
> 
> ### Summary
> 
> Make it as simple as possible to develop using the `https:` protocol in @roots/bud projects. 
> 
> See: https://github.com/roots/bud/pulls/933
> 
> ### Motivation
> 
> #### Why are we doing this?
> 
> It's increasingly important to develop with SSL enabled
> 
> #### What use cases does it support?
> 
> - dev parity
> - interoperability with other tools
> 
> #### What is the expected outcome?
> 
> A path forward for configuring Express with user supplied certs that is:
> - viable for a general audience
> - documented
> 
> #### Potential conflicts / foreseeable issues
> 
> I don't want bud to be in the business of managing and issuing certificates.
> 
> ### Additional Context
> 
> _No response_

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

---

## Post 3 by @djmtype — 2022-02-23T17:05:44Z

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

---

## Post 4 by @kellymears — 2022-02-24T15:53:52Z

thanks for your patience @djmtype!