今天在一个软件中遇到如下的错误：

D:\v4_tool\x2xxxW\x2xxxW\x2xxx-core>.\x2xxx.exe
x2xxx 4.43.0 (X2xxx, a community-driven edition of x2xxx.) Custom (go1.17.1 windows/amd64)
A unified platform for anti-censorship.
2022/11/22 20:32:56 Using default config:  D:\v4_tool\x2xxxW\x2xxxW\x2xxx-core\config.json
2022/11/22 20:32:56 [Info] main/jsonem: Reading config: D:\v4_tool\x2xxxW\x2xxxW\x2xxx-core\config.json
Failed to start app/proxyman/inbound: failed to listen TCP on 1080 > transport/internet: failed to listen on address: 127.0.0.1:1080 > transport/internet/tcp: failed to listen TCP on 127.0.0.1:1080 > listen tcp 127.0.0.1:1080: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
乍一看，就是端口占用呗，可离谱的地方在于：使用端口检查的命令根本找不着被占用的端口。
 
netstat -ano | findstr ":1080"
这我就郁闷了！心里一想，刚刚也就装了个 Docker 啊？算了，简单期间，就把 Docker 必须是重大嫌疑！
 
于是我百度了下一个新的关键词 docker 1081，还真有人和我一样：
 
 
好吧，开始修复。
 
查看禁止使用的端口号
 
netsh interface ipv4 show excludedportrange protocol=tcp
协议 tcp 端口排除范围
开始端口    结束端口
----------    --------
      1068        1167
      1168        1267
      1368        1467
      1468        1567
      1568        1667
      1668        1767
      1768        1867
      1868        1967
      1973        2072
      2180        2279
     18000       18000
     50000       50059     *
* - 管理的端口排除。
 
发现我要使用的 1081 端口，确实被禁止了
 
 
重新修改这类端口范围
 
 
C:\WINDOWS\system32>netsh int ipv4 set dynamicport tcp start=50000 num=500
又可以愉快的使用1081端口了。
				
问题描述：
今天电脑(WIN10)开机之后，发现上不了网，打开Clash for Windows v0.15.2之后：
看到端口从1080变成了0，而且我尝试把端口改回1080，没等我缓过神来端口又变回0了！
原因分析：
按照经验来说，大概率是端口冲突问题，毕竟最近我并没有修改过这个软件，或者说就没有对电脑进行异常的配置。
1. 查看日志
一般出现这类摸不着头脑的问题，首先考虑查看日志：
这是我电脑上存放日志的路径：C:\Users\Hades\.config\clash\logs
打开对应日期的l
				
nginx启动失败（bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket…permissions)
nginx启动失败
nginx启动失败（bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)）
文章目录#
nginx启动失败（
					
An attempt was made to access a socket in a way forbidden by its access permissions 问题解决
				
今天在启动nginx时，发现启动后在进程中没有nginx的进程，查看日志发现错误日志：
bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket
 in a way forbidden by its access permissions)
根据日志内容，判断可能是80端口被占用了，于是使用netstat ...
				
This error occurs when you try to access a closed SQLiteDatabase object. This can happen when you try to perform a database operation on a SQLiteDatabase object which has already been closed.
To resolve this error, you need to ensure that you are not trying to access a closed SQLiteDatabase object. You can do this by checking the state of the SQLiteDatabase object before performing any operation on it. 
Here is an example of how you can avoid this error:
1. Open the SQLiteDatabase object:
SQLiteDatabase db = dbHelper.getWritableDatabase();
2. Check the state of the SQLiteDatabase object:
if (db.isOpen()) {
    // Perform database operations here
} else {
    // Handle the case where the SQLiteDatabase object is closed
3. Close the SQLiteDatabase object when you are done with it:
db.close();
By following these steps, you can avoid the IllegalStateException: attempt to re-open an already-closed object: SQLiteDatabase error.