# Dfx 0.9.3 is promoted
**URL:** https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656
**Category:** Developers
**Created:** [March 23, 2022, 9:10pm UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656 "2022-03-23T21:10:17Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@ericswanson](https://forum.dfinity.org/u/ericswanson)
#### Post date: [March 23, 2022, 9:10pm UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/1 "2022-03-23T21:10:17Z")
Release notes: [Highlights of what’s new in 0.9.3 :: Internet Computer](https://smartcontracts.org/docs/release-notes/0.9.3-rn.html)
The main changes were to update these dependencies:
- Replica to blessed commit d004accc3904e24dddb13a11d93451523e1a8a5f
- Motoko to 0.6.25
- icx-proxy, which is now static-linked
---
### Author:  [@skilesare](https://forum.dfinity.org/u/skilesare)
#### Post date: [March 24, 2022, 1:03am UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/2 "2022-03-24T01:03:30Z")
Is there a change log for motoko?
---
### Author:  [@ericswanson](https://forum.dfinity.org/u/ericswanson)
#### Post date: [March 24, 2022, 1:12am UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/3 "2022-03-24T01:12:28Z")
>
---
### Author:  [@AlliDoizCode](https://forum.dfinity.org/u/AlliDoizCode)
#### Post date: [March 24, 2022, 3:11am UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/4 "2022-03-24T03:11:29Z")
does this mean I need to change my implementation of my streaming strategy or will it just start streaming chunks again? I am using an implementation similar to this [non-fungible-token/http.mo at main · DepartureLabsIC/non-fungible-token · GitHub](https://github.com/DepartureLabsIC/non-fungible-token/blob/main/src/http.mo) and are replicas currently running these changes
---
### Author:  [@jzxchiang](https://forum.dfinity.org/u/jzxchiang)
#### Post date: [March 24, 2022, 6:22am UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/5 "2022-03-24T06:22:10Z")
Unfortunately, when I upgrade and run `dfx start` in 0.9.3, it now no longer respects the networks.local.bind IP address + port combo that I specify in my dfx.json, and instead picks a random port…
In fact, the first line of `dfx start` is now:
```auto
binding to: 192.168.1.67:51869
```
My dfx.json contains this:
```auto
"dfx": "0.9.3",
"networks": {
"local": {
"bind": "192.168.1.67:8000",
"type": "ephemeral"
}
},
```
Another issue is when I ctrl+C in a terminal with a running `dfx start`. It takes more than a minute to stop the replica and return control back to the user. I don’t know why it takes so long…
---
### Author:  [@ericswanson](https://forum.dfinity.org/u/ericswanson)
#### Post date: [March 24, 2022, 5:18pm UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/6 "2022-03-24T17:18:50Z")
That’s the dfx internal webserver, which is only used to serve candid interfaces.
Later on, you should see something like this, which corresponds to your bind address:
```auto
Mar 24 10:17:01.427 INFO Log Level: INFO
Mar 24 10:17:01.428 INFO Starting server. Listening on http://127.0.0.1:8000/
```
I just ran that, and then edited dfx.json to change the port to 8003, after which:
```auto
Mar 24 10:17:25.716 INFO Log Level: INFO
Mar 24 10:17:25.717 INFO Starting server. Listening on http://127.0.0.1:8003/
```
---
### Author:  [@jzxchiang](https://forum.dfinity.org/u/jzxchiang)
#### Post date: [March 25, 2022, 2:26am UTC](https://forum.dfinity.org/t/dfx-0-9-3-is-promoted/11656/7 "2022-03-25T02:26:28Z")
Ah the issue was that I didn’t run `dfx start --clean`. Sorry for the trouble.