CrushFTP Support Forums
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: spinkb
Forum Index » Profile for spinkb » Messages posted by spinkb
Author Message
Possibly in your User Manager, WebInterface section, customizations list you have these items being hidden?

Can you provide a screenshot of what you see as well?

Thanks,
Ben
Unfortunately, this isn't possible. The form is for the user, and not specific to a particular folder. We will keep this in mind for a future update though...

Thanks,
Ben
Fixed in new build. Update now.

Thanks,
Ben
In your prefs, encryption, SSL tab, you can put checkmarks on all the ciphers you want to disable. Then test again.

If your on CrushFTP 7.2, the upper right to the cipher list has a defaults button to reset just the ciphers.

Thanks,
Ben
You cannot use FolderMonitor. Use the Jobs tab, and configure jobs to go after these locations to look for old files.

So a Find, then a Delete. But for testing just do a Find, then a Wait. Make sure its getting the files expected before you let it start deleting.

Thanks,
Ben
No special apache config should be done. Undo that.

In CrushFTP, only do the reverse proxy part, not where crush is behind a reverse proxy. You are going to have CrushFTP act as your reverse proxy.

Domain: *
URL: http://127.0.0.1:8081/ <-------run apache using plain http on pro 8081
path: /myregistration/

CrushFTP owns port 443, apache uses 8081 for plain HTTP.

Thanks,
Ben
Edit your prefs.xml file.

Set "Access-Control-Allow-Origin" to be "http://yourdomain.com"

Does that resolve it?

Technically being able to embed your site in a frame is considered a security issue, so by default its not allowed.

Thanks,
Ben
Check the User Manager, admin, limited admin button.

Make sure the one and only checkbox they have is the very top one. Enabling other checkboxes will conflict with that...

Thanks,
Ben
A limited admin is just a limited admin. They can't be a prefs admin, or any other role except limited admin.

I would also suggest using a _ instead of a space as a space might have URL encoding issues. So rename the user and group names to be "External_Users".

Let me know,
Ben
Can you email us directly at support?

May need to do a screen sharing session to see what is going on.

Thanks,
Ben
This isn't a ban.

This is a config in the User Manager blocking this IP for this username. So check your User Manager configuration.

Thanks,
Ben
OK, but your missing the "/" item like your real user int he User Manager had, and you don't have a S3_REST item either... You allow access to a non existent /S3/ path, so you have differences in many areas.

Your VFS.XML returned by the web call should match identically to a valid VFS.XML created from the User Manager. It needs the / item in it, and also the /NAME/ of your VFS items your returning in the main call we have been discussing so far.

So, for your next reply here, please include both the VFS.XML and the VFS items that are returned with your S3 keys removed.

Thanks,
Ben
What about the vfs.xml reply item for the web application. What are the contents of that xml?

Thanks,
Ben
You must use the full path to your java install and not rely on the PATH. I suspect your PATH is not set unless you use some customer environment variables in the config.

You see it in your DOS window since windows is doing that automatically for you.

But if you just use the full C:\Program Files\Java\jdk1.7.0_21\bin\java.exe as the binary things will be fine.

Thanks,
Ben
Updating has no effect on Share links.

Either the prior links were expired, or your TempAccount user was disabled, etc. But an upgrade cannot affect the temp shares created in any way. They don't even touch the same folders.

Thanks,
Ben
Undo your changes to default and TempAccount. Your making things unsafe if you are modifying their VFS. They should not have a VFS defined, otherwise *everyone* may get your change since nearly everyone is inheriting from them.

Email us at support and we will continue this to figure out what is going wrong.

Thanks,
Ben
530 access denied means they typed a bad username or password. Nothing to dow with ports or anything else.

Thanks,
Ben
That was mainly a question...

I'm wondering which user has your create dir button. Does TempAccount have it? Does default have it?

Does the user you are currently logged in with have it?

Thanks,
Ben
Check the TempAccount, do they have a Create Dir button on them, or are they inheriting from the default user?

Thanks,
Ben
This isn't correct still, you put them int he wrong area.

<data type="vector">
<data_subitem type="properties">
<url>s3://***:***s3.amazonaws.com/dev-ftp-storage/</url>
<type>DIR</type>
<secretKeyID>***</secretKeyID>
<secretKey>***</secretKey>
</data_subitem>
</data>

Chang like that.

Thanks,
Ben
No, I meant in your XML reply to the WebApplication plugin, you didn't include those two fields. So The S3 VFS your trying tor turn isn't complete.

I'm not referring to your censoring those keys here, which you should absolutely be doing.

Thanks,
Ben
You said its only one user...so put this all in the CrushTask.

Your only using FolderMonitor to run a crush task, folder monitor is not going to do anything else.

FolderMonitor finds files older than 90 days.
CrushTask: Rename (same name, just update modified date)
Move: put files in subfolder
Email: email person their are files about to be purged.

FolderMonitor finds files older then 4 days in the subfolder
Email: email person their files have been deleted
Delete: files

--Ben
You didn't include these items...

<secretKeyID>***</secretKeyID>
<secretKey>***</secretKey>

Thanks,
Ben
You must set the port range, or else all FTPES connections will fail. Which means everyone who uses FZ or Cyberduck might have issues since they both use FTPES by default.

Set the range to 2000-2100 and forward on your router too.

Thanks,
Ben
We don't seem to have a test for FTPES. :( Didn't realize that until now.

Do you have a PASV port range forwarded? 2000-2100? On the port and your router?

Thanks,
Ben
Its only the latest FZ that starts using FTPES by default.

So the diagnostic test passed for FTP or FTPES?

Thanks,
Ben
Does your server work for FTPES on our diagnostic page test?

http://crushftp.com/diagnostics.jsp

If not your ports aren't forwarded on your router for PASV. We suggest 2000-2100, this needs to be configured on the FTP port, and your router.

Thanks,
Ben
We provide a sample Xml item here:

http://www.crushftp.com/crush7wiki/Wiki.jsp?page=WebApplicationSource

As well as the source. But look t the XML as that will help you.

Thanks,
Ben
Your bat file doesn't run.

Java is not a valid command in your DOS prompt since java is not in your OS path.

Specify the full auth to your java.exe.

Something like:

C:\Program Files\Java\jre7\bin\java.exe

Thanks,
Ben
I think for your scenario, you just need to use a Folder Monitor to find the files that are older than a certain date...

But the issue is that folder monitor is going to find files every minute that are older...

So on your first find, you need to move them into a sub folder, like "_TO_BE_DELETED".

Then only scan that sub folder for files older than 32 days or 92 days, etc...2 days more. So they can move them out of there...

But CrushFTP always sees the modified date. So if they are being moved out of there, you are going to need to "touch" the file to make it be modified with todays date. Otherwise you put it back in the main folder, folder monitor grabs it and puts it in the to be deleted folder, then it checks that folder and deletes it instantly as the file is now old enough...

So its a combination of moving the file, resetting its date, and the can move it back to the main folder.

This is just two task steps in CrushFTP being called by folder monitor.
Rename (and set to todays date flag), then move to _TO_BE_DELETED

Then a separate folder monitor to find files older than 2 days in that folder it was moved to. (_TO_BE_DELETED)

Thanks,
Ben
If you know REGEX, you could do it with that...

You can do regex patterns with the prefix:


REGEX:somepattern

So you could then do a reverse pattern scenario. But we don't provide regex support in how to format your patterns as that gets rather complicated...

Might also be able to do:
!*[ABC]*

That may also give you the desired results.

Thanks,
Ben
I replied in email...but I suspect you are not resetting the date in modified_times in order to tell CrushFTP to update its cached version of the user.

Thanks,
Ben
This helps more...I replied to your email too.

Running jobs is an enterprise only feature. Normal licenses cannot run or schedule jobs. That is the limitation your hitting, nothing to dow with your SQL config.

Sorry,
Ben
I just checked how things work, and we are always executing CrushFTP7.app/Contents/MacOS/CrushFTP.command

That tried to use the java8 in your plugins.

So the auth button should really be working...

Is CrushFTP in your applications folder? With the name "CrushFTP7_OSX"?

No spaces in its folder path?

Thanks,
Ben
Need to see the full log leading up to the error message.

Has nothing to do with that filename.

Has everything to do with what folder they attempted to upload into...like uploading to "/" when that isn't a writable location. Most likely the client has a bug in how its handling all the files and getting confused when its doing a write. The log will reveal the issue.

Thanks,
Ben
There might be a bug where we are expecting the Java 6 to be installed "java" on the command line as well as the Internet plugin for Java 8 which is what it was launched with.

However, if you just install the daemon, then there isn't an issue. I'll let you know what I figure out.

Thanks,
Ben
Maybe that is the clue I needed...

Use the prefs, encryption, SSL tab. Do it there instead of on the individual port item...maybe that is the issue?

I've now had the old links removed, missed those.

Thanks,
Ben
Just for testing...try keeping the password as something really simple, like "password".

Can you do the whole process that way? We can change it later on using Portecle.

If your using a strong key...yes, you do have the worry bout the export restriction bureaucracy. Its a political nonsense decision from probably 15 years ago? That may in fact be what is causing issues...it can't read the key because it was saved in such a strong format.

So follow the top entry here to get updated policy files installed. (All they literally do is change a piece of text that says you can do keys of unlimited size. Nothing special, just a political decision.

http://www.crushftp.com/crush7wiki/Wiki.jsp?page=FAQ

Thanks,
Ben
Is this CrushFTP 7.2?

This error means the password you have in the generate CSR step isn't correct, so it can't open the keystore to generate the CSR>

Re-enter the password ons step 2.

Thanks,
Ben
OK, because the process is all built in and much easier in v7... :)

--Ben
You have missed something in the steps.

You started over with a new keystore at some point. So re-sign your keystore again by getting a CSR from the private key, and improving the CA reply.

The CA reply you have now is not for the private key in this keystore...so its useless.

But more importantly...why aren't you using CrushFTP 7? And then why aren't you following the v7 guide?

There is no reason to still be on v6, you may be putting your server at risk if you don't keep things somewhat updated.

Thanks,
Ben
Send an email to support asking for a trial enterprise key. They will reply back with one.

Thanks,
Ben
You login...CrushFTP assigned the cookie to you and tells the browser "set-cookie: ..................."

Your browser honors that, and remembers the cookie, and as long as its referenced from then on, you can do anything you want in that login.

Thanks,
Ben
Click update now, and it will support the {user_name} variable in the additional paths area. But you must update first.

Thanks,
Ben
The login system in 6.5 and 7.2 is the same. So what worked in 6.5 will work in 7.2.

But 7.2 has more features on the login page...so you will be missing those if you keep your old login page. But it should still work just fine.

MagicDir and such haven't changed.

Thanks,
Ben
Remove the windows service, and then reinstall the windows service.

Does the service work then?

Thanks,
Ben
To match that dir structure, CrushTask has to be used.

Send us an email at support and I'll give you a user.xml file that has the event already created.

You just need to update the paths in it to point to your folder location and it will do exactly what you are looking for.

Thanks,
Ben
The folder name can't be their username because it would cause a collision of two folders at the same level having the same name....how would they be able to distinguish which was which?

It is possible, but creating the VFS item with a custom name would have to be done through a login event and crush task configured item. This could make the VFS item pointer and VFS.XML file with the permissions on demand at login.

Thanks,
Ben
In the User Manager, if your not using hashing, double clicking on the label Password: next to the field will reveal the password. If its hashed though, it can't be revealed.

For the scenario you described, you could simply make this config on the default user with a VFS item referencing a variable.

file://somepath/to/folder/Receive/%username%/

and another item

file://somepath/to/folder/Deposit/%username%/

And name one Receive, and the other Deposit. user logs in,s is both folders, chooses which to go into and that is it.

All users can link to this common VFS. This doesn't create the folders for you, but allows for the general pointing towards the folders. If you needed the folders created automatically too, you could have a login event referenced as well that generated the folders. You would only need to do this one time, and allow users to be inheriting this setting automatically.

Thanks,
Ben
Your notify email for this forum is incorrect and the email is bouncing...

I'll reply back here in a little bit.
 
Forum Index » Profile for spinkb » Messages posted by spinkb
Go to:   
Powered by JForum 2.1.8 © JForum Team