# Network error when deleting form
**URL:** https://community.nocodb.com/t/network-error-when-deleting-form/1579
**Category:** Self-Host
**Created:** [January 9, 2025, 2:47am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579 "2025-01-09T02:47:04Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@andrew\_hou](https://community.nocodb.com/u/andrew_hou)
#### Post date: [January 9, 2025, 2:47am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/1 "2025-01-09T02:47:04Z")
I just deployed NOCODB in my linux server using default pg docker-compose file.
It is amazing, the app itself works fine.
But when i try to delete a form it failed and report a network error, as the browser console show below
Bye the way, URL of my app is [http://172.18.231.46:8080](http://172.18.231.46:8080). Should I change docker-compose file according to this url? How should I do that ?
I am a student on this so apologize for this dummy questions.
Much appreciate if anyone can give me any clue.
---
### Author:  [@pranavxc](https://community.nocodb.com/u/pranavxc)
#### Post date: [January 9, 2025, 5:52am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/2 "2025-01-09T05:52:29Z")
To assist you better, please provide the following details:
1. The version of the NocoDB Docker image you’re using. If possible, please include your Docker Compose file as well.
2. The Docker logs for the application. Specifically, the backend error logs(docker logs) will be helpful.
3. The HTTP response details captured in your browser’s network tab.
Additionally, ensure that you configure the `NC_PUBLIC_URL` environment variable with the correct URL. This is essential for ensuring that all functionalities work as expected. You can find more information about environment variables in our [documentation here](https://docs.nocodb.com/getting-started/self-hosted/environment-variables/#frontend).
---
### Author:  [@andrew\_hou](https://community.nocodb.com/u/andrew_hou)
#### Post date: [January 15, 2025, 8:10am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/3 "2025-01-15T08:10:29Z")
Thank you so much for helping.
Issue: cannot delete a form
NocoDB version: 0.260.0
docker-compose.yml:
```auto
version: '2.1'
services:
nocodb:
depends_on:
root_db:
condition: service_healthy
environment:
NC_DB: "pg://root_db:5432?u=postgres&p=password&d=root_db"
VIRTUAL_HOST: http://172.18.231.46:8080
NC_PUBLIC_URL: http://172.18.231.46:8080
image: "nocodb/nocodb:latest"
ports:
- "8080:8080"
restart: always
volumes:
- "nc_data:/usr/app/data"
root_db:
environment:
POSTGRES_DB: root_db
POSTGRES_PASSWORD: password
POSTGRES_USER: postgres
healthcheck:
interval: 10s
retries: 10
test: "pg_isready -U \"$$POSTGRES_USER\" -d \"$$POSTGRES_DB\""
timeout: 2s
image: postgres:16.6
restart: always
volumes:
- "db_data:/var/lib/postgresql/data"
volumes:
db_data: {}
nc_data: {}
```
docker logs find nothing related:
browser response:
---
### Author:  [@dstala](https://community.nocodb.com/u/dstala)
#### Post date: [January 17, 2025, 4:22am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/4 "2025-01-17T04:22:51Z")
Does the form still persist on page reload? Issue created [here](https://github.com/nocodb/nocodb/issues/10295) to track it further
---
### Author:  [@andrew\_hou](https://community.nocodb.com/u/andrew_hou)
#### Post date: [January 17, 2025, 5:57am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/5 "2025-01-17T05:57:54Z")
Yes, it persist after page reload.
thank u
---
### Author:  [@pranavxc](https://community.nocodb.com/u/pranavxc)
#### Post date: [January 23, 2025, 6:15am UTC](https://community.nocodb.com/t/network-error-when-deleting-form/1579/6 "2025-01-23T06:15:49Z")
From the network tab, it appears the issue is with the table delete API call, not the form delete API. The error `ERR_CONNECTION_RESET` suggests that the connection is being interrupted, likely due to your browser, system firewall, or security software blocking the request. Please check if any browser extensions, antivirus software, or firewall settings might be causing this issue.
To confirm, you can try the following steps:
1. Test the operation on a different machine to see if the issue persists.
2. Copy the cURL command for the request from the network tab and execute it directly in your terminal to rule out browser-related problems.