pureftpd安装问题请求帮助

ifre

第一次安装管理员那个Lnmp包之后安装pureftpd是安装成功了.

现在发现一个问题.就是那个第四步：

哪里的密码到底是默认,还是需要修改. 我第一次安装成功的时候是默认的.
后来几次我改了哪里的密码,安装成功了。但是FTP就一直登陆不上去. 真是搞不懂了.

licanqiji

原帖由 ifre 于 2010-8-8 15:01 发表
第一次安装管理员那个Lnmp包之后安装pureftpd是安装成功了.

现在发现一个问题.就是那个第四步：

哪里的密码到底是默认,还是需要修改. 我第一次安装成功 ...

看看 第6部成功了没有你覆盖了没有 按照教程一步一步来 肯定会成功

ifre

肯定成功了啊. 都提示congratulations 了.

但是就是无法通过FTP登陆不了. 改了密码就不行了，难道你们都是使用的默认密码？？？

licess

按https://www.vpser.net/manage/lnmp-pureftpd-cp.html文章末尾方法解检查一下。

27198277

1. # Force an IP address in PASV/EPSV/SPSV replies. - for NAT.
   
2. # Symbolic host names are also accepted for gateways with dynamic IP
   
3. # addresses.
   
4. 
   
5. # ForcePassiveIP 192.168.0.1
   
6. 
   
7. 
   
8. 
   
9. # Upload/download ratio for anonymous users.
   
10. 
    
11. # AnonymousRatio 1 10
    
12. 
    
13. 
    
14. 
    
15. # Upload/download ratio for all users.
    
16. # This directive superscedes the previous one.
    
17. 
    
18. # UserRatio 1 10
    
19. 
    
20. 
    
21. 
    
22. # Disallow downloading of files owned by "ftp", ie.
    
23. # files that were uploaded but not validated by a local admin.
    
24. 
    
25. AntiWarez yes
    
26. 
    
27. 
    
28. 
    
29. # IP address/port to listen to (default=all IP and port 21).
    
30. 
    
31. # Bind localhost,21
    
32. 
    
33. 
    
34. 
    
35. # Maximum bandwidth for anonymous users in KB/s
    
36. 
    
37. # AnonymousBandwidth 8
    
38. 
    
39. 
    
40. 
    
41. # Maximum bandwidth for *all* users (including anonymous) in KB/s
    
42. # Use AnonymousBandwidth *or* UserBandwidth, both makes no sense.
    
43. 
    
44. # UserBandwidth 8
    
45. 
    
46. 
    
47. 
    
48. # File creation mask. : .
    
49. # 177:077 if you feel paranoid.
    
50. 
    
51. Umask 133:022
    
52. 
    
53. 
    
54. 
    
55. # Minimum UID for an authenticated user to log in.
    
56. 
    
57. MinUID 100
    
58. 
    
59. 
    
60. 
    
61. # Allow FXP transfers for authenticated users.
    
62. 
    
63. AllowUserFXP no
    
64. 
    
65. 
    
66. 
    
67. # Allow anonymous FXP for anonymous and non-anonymous users.
    
68. 
    
69. AllowAnonymousFXP no
    
70. 
    
71. 
    
72. 
    
73. # Users can't delete/write files beginning with a dot ('.')
    
74. # even if they own them. If TrustedGID is enabled, this group
    
75. # will have access to dot-files, though.
    
76. 
    
77. ProhibitDotFilesWrite no
    
78. 
    
79. 
    
80. 
    
81. # Prohibit *reading* of files beginning with a dot (.history, .ssh...)
    
82. 
    
83. ProhibitDotFilesRead no
    
84. 
    
85. 
    
86. 
    
87. # Never overwrite files. When a file whoose name already exist is uploaded,
    
88. # it get automatically renamed to file.1, file.2, file.3, ...
    
89. 
    
90. AutoRename no
    
91. 
    
92. 
    
93. 
    
94. # Disallow anonymous users to upload new files (no = upload is allowed)
    
95. 
    
96. AnonymousCantUpload no
    
97. 
    
98. 
    
99. 
    
100. # Only connections to this specific IP address are allowed to be
     
101. # non-anonymous. You can use this directive to open several public IPs for
     
102. # anonymous FTP, and keep a private firewalled IP for remote administration.
     
103. # You can also only allow a non-routable local IP (like 10.x.x.x) to
     
104. # authenticate, and keep a public anon-only FTP server on another IP.
     
105. 
     
106. #TrustedIP 10.1.1.1
     
107. 
     
108. 
     
109. 
     
110. # If you want to add the PID to every logged line, uncomment the following
     
111. # line.
     
112. 
     
113. #LogPID yes
     
114. 
     
115. 
     
116. 
     
117. # Create an additional log file with transfers logged in a Apache-like format :
     
118. # fw.c9x.org - jedi [13/Dec/1975:19:36:39] "GET /ftp/linux.tar.bz2" 200 21809338
     
119. # This log file can then be processed by www traffic analyzers.
     
120. 
     
121. # AltLog clf:/var/log/pureftpd.log
     
122. 
     
123. 
     
124. 
     
125. # Create an additional log file with transfers logged in a format optimized
     
126. # for statistic reports.
     
127. 
     
128. # AltLog stats:/var/log/pureftpd.log
     
129. 
     
130. 
     
131. 
     
132. # Create an additional log file with transfers logged in the standard W3C
     
133. # format (compatible with most commercial log analyzers)
     
134. 
     
135. # AltLog w3c:/var/log/pureftpd.log
     
136. 
     
137. 
     
138. 
     
139. # Disallow the CHMOD command. Users can't change perms of their files.
     
140. 
     
141. #NoChmod yes
     
142. 
     
143. 
     
144. 
     
145. # Allow users to resume and upload files, but *NOT* to delete them.
     
146. 
     
147. #KeepAllFiles yes
     
148. 
     
149. 
     
150. 
     
151. # Automatically create home directories if they are missing
     
152. 
     
153. CreateHomeDir no
     
154. 
     
155. 
     
156. 
     
157. # Enable virtual quotas. The first number is the max number of files.
     
158. # The second number is the max size of megabytes.
     
159. # So 1000:10 limits every user to 1000 files and 10 Mb.
     
160. 
     
161. #Quota 1000:10
     
162. 
     
163. 
     
164. 
     
165. # If your pure-ftpd has been compiled with standalone support, you can change
     
166. # the location of the pid file. The default is /var/run/pure-ftpd.pid
     
167. 
     
168. #PIDFile /var/run/pure-ftpd.pid
     
169. 
     
170. 
     
171. 
     
172. # If your pure-ftpd has been compiled with pure-uploadscript support,
     
173. # this will make pure-ftpd write info about new uploads to
     
174. # /var/run/pure-ftpd.upload.pipe so pure-uploadscript can read it and
     
175. # spawn a script to handle the upload.
     
176. 
     
177. #CallUploadScript yes
     
178. 
     
179. 
     
180. 
     
181. # This option is useful with servers where anonymous upload is
     
182. # allowed. As /var/ftp is in /var, it save some space and protect
     
183. # the log files. When the partition is more that X percent full,
     
184. # new uploads are disallowed.
     
185. 
     
186. MaxDiskUsage 99
     
187. 
     
188. 
     
189. 
     
190. # Set to 'yes' if you don't want your users to rename files.
     
191. 
     
192. #NoRename yes
     
193. 
     
194. 
     
195. 
     
196. # Be 'customer proof' : workaround against common customer mistakes like
     
197. # 'chmod 0 public_html', that are valid, but that could cause ignorant
     
198. # customers to lock their files, and then keep your technical support busy
     
199. # with silly issues. If you're sure all your users have some basic Unix
     
200. # knowledge, this feature is useless. If you're a hosting service, enable it.
     
201. 
     
202. CustomerProof yes
     
203. 
     
204. 
     
205. 
     
206. # Per-user concurrency limits. It will only work if the FTP server has
     
207. # been compiled with --with-peruserlimits (and this is the case on
     
208. # most binary distributions) .
     
209. # The format is : :
     
210. # For instance, 3:20 means that the same authenticated user can have 3 active
     
211. # sessions max. And there are 20 anonymous sessions max.
     
212. 
     
213. # PerUserLimits 3:20
     
214. 
     
215. 
     
216. 
     
217. # When a file is uploaded and there is already a previous version of the file
     
218. # with the same name, the old file will neither get removed nor truncated.
     
219. # Upload will take place in a temporary file and once the upload is complete,
     
220. # the switch to the new version will be atomic. For instance, when a large PHP
     
221. # script is being uploaded, the web server will still serve the old version and
     
222. # immediatly switch to the new one as soon as the full file will have been
     
223. # transfered. This option is incompatible with virtual quotas.
     
224. 
     
225. # NoTruncate yes
     
226. 
     
227. 
     
228. 
     
229. # This option can accept three values :
     
230. # 0 : disable SSL/TLS encryption layer (default).
     
231. # 1 : accept both traditional and encrypted sessions.
     
232. # 2 : refuse connections that don't use SSL/TLS security mechanisms,
     
233. # including anonymous sessions.
     
234. # Do _not_ uncomment this blindly. Be sure that :
     
235. # 1) Your server has been compiled with SSL/TLS support (--with-tls),
     
236. # 2) A valid certificate is in place,
     
237. # 3) Only compatible clients will log in.
     
238. 
     
239. # TLS 1
     
240. 
     
241. 
     
242. 
     
243. # Listen only to IPv4 addresses in standalone mode (ie. disable IPv6)
     
244. # By default, both IPv4 and IPv6 are enabled.
     
245. 
     
246. # IPV4Only yes
     
247. 
     
248. 
     
249. 
     
250. # Listen only to IPv6 addresses in standalone mode (ie. disable IPv4)
     
251. # By default, both IPv4 and IPv6 are enabled.
     
252. 
     
253. # IPV6Only yes
     
254. 
     
255. # UTF-8 support for file names (RFC 2640)
     
256. # Define charset of the server filesystem and optionnally the default charset
     
257. # for remote clients if they don't use UTF-8.
     
258. # Works only if pure-ftpd has been compiled with --with-rfc2640
     
259. 
     
260. # FileSystemCharset big5
     
261. # ClientCharset big5
     
262. AllowOverwrite on
     
263. AllowStoreRestart on

复制代码