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
Put a wait task before the rename...wait for say 3 minutes, then the rename.

Or rename, on failure, wait 3 minutes, another rename task (not looping back to the other one), if that too fails, then email yourself an email.


rename1 -> move
---on fail: wait 3 minutes -> rename2 -> move
-------------------------------------on fail: email admin
Unlikely CrushFTP holding it open...

Virus scanning software?

Can you manually rename it later on?
The rename is failing due to a permissions issue on the OS, or the user has the file still in use...and your OS doesn't allow renaming an in use file (windows).

Its one of those two reasons...or the file didn't exist due tot he user renaming it or something...

Thanks,
Ben
The expiration task cannot wait that long.

Instead use expiration to copy the files to another folder, don't preserve modified date, and have a folder monitor set to cleanup that folder when times reach 30 days old.


How do you know the task hasn't been running? What is in your log?

Thanks,
Ben
Do you have the localization selector?

Can you change to the german localization and does it start working then?

Thanks,
Ben
Expired and enabled are unrelated.

A user can't login if the account is expired, or its disabled.

Thanks,
Ben
And just to followup and confirm your expectation on the HomeDir plugin, i wanted to provide more about the features in it.

You can set the unique time stamp, and prepend the username. If the user were to login twice in a time period that still creates the same home folder, then it will be erased if the allow access to old home folders is not enabled.

The allow access doesn't mean it will let the user access prior date stamped home folders, it means their home folder won't be erased on login if you have it set to always generate.

As far as I can tell looking at the history of this plugin, it has been this way forever. So if you were expecting something else, then that would be wrong.

Thanks,
Ben
This issue may have been a bug with our SFTP VFS. Was this with SFTP? We just fixed a bug with it.

Let me know,
Ben
I think new members aren't allowed to put screenshots is all...over time you will be allowed.

Can you email us directly at support and include the screenshots so we can see the differences?

Are you using the extra vfs, or other linked vfs scenarios?
1.) Delete your user/pass for the email. Then exchange will allow the connection. v5 always tried first with no auth, then tried auth. v6 and v7 just honor your auth settings, and they need to be blank.

2.) Do you have protocol restrictions for the users only allowing one protocol? Or max logins configured on the user?

Thanks,
Ben
The on Connect event can trigger a crush task, and an email event in it, you can then reference each from relents value with the {item_name} type reference, or {this_is_my_field} etc. Everything inside the curly brackets is the form elements name.

Thanks,
Ben
That is all apache config stuff...I'm not an expert in it. I fight with apache every time I have to make changes in my own config...

Now I use CrushFTP as my reverse proxy, and redirect from it to other domains.

But you can do this in apache...just have to get your config right. Order matters, location of config matters (inside a <virtual tag or something like that, I forget. I'm just not familiar with exact syntax in apache...that is outside the scope of CrushFTP, and its something you have to configure yourself. CrushFTP is working fine, its just your apache config is forwarding more than you want to it.

--Ben>
Apache can do different configs based on a domain...that is all in your apache config.

So its possible, you just have an issue in apache currently.
If HTTPS is also owned by Apache, you have to do the exact same scenario for that port as well.

I might suggest just a bit of custom javascript on the login page to look to see if its HTTPS or not, and redirect their browser page to https if its not.

Thanks,
Ben
Update to 7.1, this should fix the issue.

There is something going wrong with your sessions here, and 7.1 has a lot of fixes for sessions.

Thanks,
Ben
In the prefs, http port, advanced...your reverse proxy path should be '/' and not '/crushftp/'.

Thanks,
Ben
If you hard code the CrushFTP IP, you have an issue in that 127.0.0.1 isn't being used so you have to point Apache to the hard coded IP. By leaving it as "lookup", its bound to all IPs and is fine.

When you get the selected resource was not found, we need to see the CrushFTP.log entries, and we need to see *exactly* what you put in your apache config, and the CrushFTP prefs, http port, advanced, reverse proxy config area.

Thanks,
Ben
Still a little confused...

So you a re using homedir, and you have it enabled to allow access to old homers, and its sometimes allowing old access, and sometimes not?
I'm not quite sure what you mean by detecting the home folder...there is no method that does what you describe there.

Please explain more.

Thanks,
Ben
The latest build now supports multithreaded listings on SFTP too. So both FTP and SFTP can do this.

However, in my testing, the OpenSSH client doesn't bother displaying the listing until it has all results...it caches it in memory before showing it. This isn't because of CrushFTP not providing it in chunks though anymore, as we just added that capability, and verified in t eh code it is actually occurring.

So its up to your SFTP client to do multithreading to display the list as its incoming.

7.1.0_18+

Thanks,
Ben
What exact version is this?

Thanks,
Ben
Look at the CrushFTP.log. It should be logging all those failed attempts...so you know what machine tried to connect, and what surname its trying with to give you an idea of what process was expecting to be able to connect.

Thanks,
Ben
Try FTP as a test, does it work there? That will help us to know if the multithreading is working.

The web stands no chance of displaying this much without a massive memory chunk assigned to CrushFTP.

Let me know,
Ben
Change the CrushFTP port 443 to be 4443.

Then try your HTTPS port. If you can still connect...even if it drops you quickly, then something else is running using port 443. I would assume IIS.

Remove IIS, or change IIS to use some other port so CrushFTP can get the port instead.

Thanks,
Ben
That sounds more like your IP has been banned, or you tried configuring the SSL to use a non existent keystore or something besides the defaults.

Out of the box, HTTPS is operations and ready.

To make your server trusted, you definitely need to purchase one, but its functional with your usual browser warnings at any time.

What is logged on your attempts, and what exact CrushFTP version is this?

Thanks,
Ben
Only by having some custom javascript in the prefs, WebInterface, area.

You could make changes there sand change the message you impose using javascript.
I'll look at it, I have not used docker before. First glance it doesn't look like a good fit... But I'll try more.

CrushFTP is already running as a java process. Therefore its OS independent, and mainly just a zip you expand. No real dependancies. I understand the need for what they are doing for some other larger projects that are just a mess of open source tools and such...but CrushFTP isn't that complex in how you set it up and run it. You could literally just have a zip you expand and double click on if you like...

I'll report back here on what I decide.

--Ben
This suggest some and data in your sessions.obj file.

When adjusting the server memory, stop the service, delete sessions.obj, and start the service.

Thanks,
Ben
I suggestion the service/wrapper.conf file, adjust the memory line to be 1024 or 2048.

Possibly there is something causing the server to run out of memory and stop working...then the wrapper restarts CrushFTP when it detects the server is down.

This would explain customers having strange issues too...

Thanks,
Ben
The 127.0.0.1 messages happen for all SFTP connections. They are normal.

These messages I want to see more details when why occur...

java.lang.ClassNotFoundException: crushftp.server.ServerSession
java.io.IOException: Unable to establish loopback connection

What OS is this?

If you look at the admin in CrushFTP, what is the memory usage like, number of threads like?

Thanks,
Ben
I'll consider this for a future update though, we are planning to redo the reporting system.

--Ben
Its unlikely to be possible. Maybe for HTTP(s) it can as that includes some additional headers for the client's true IP. That way a client can be banned correctly, but you always have to have the load balancer in the never ban list to protect things.

The load balancer is using the actual IP...so that is the only IP CrushFTP can ever see.

Thanks,
Ben
There isn't a way to choose where it redirects to...

If your on 7.1_13+ though, it will start its search for the first http port it finds from the current HTTP port its on. So just by organizing the HTTPS port to be after the HTTP port, you will have success.

Thanks,
Ben
Waiting for your direct email to support. We have a solution for you.

Just click update now and you will have a new field to control the MAC algorithm just like the cipher algorithm list.

Thanks,
Ben
This is not controllable. Why is it you want to change it? This isn't a cipher being used for actual file transfer or login, etc.

Is there a real issue for controlling the MAC algorithms?

Thanks,
Ben
We should be updated on that part of SFTP in the next couple months. When 7.0 was initially released we were using v5 of SFTP, but had to roll back due to stability issues in the library we relied on. We have not had a chance to go back and try and implement that library again. We definitely will, but it wasn't smooth last time so we need to do more testing.

No specific "roadmap", but we do have a continuous queue of requests waiting to be worked on. You can expect us to have some more native clients to interact with CrushFTP. You see that currently with our outlook plugin, and CrushFTPDrive, CrushSync, etc. So we are looking at ways to make working with CrushFTP work more natively. This includes iOS and android apps soon too.

Thanks,
Ben
What about just using the reports? You can schedule a report to run, and I believe there is a report that will do what you want. You can export the data as CSV, or even email it out.

So I think you are already covered for what you need.

Thanks,
Ben
In the admin, reports, use the "ExportUserPass" report.

Thanks,
Ben
Cyberduck is free, and is quite good for its usage. But for this user...I would just recommend the WebInterface instead...

Thanks,
Ben
Brian,

Let me apologize for the delay. We normally get an email notification on forum posts so we can come in and answer questions. Someone how your email notification didn't reach our inbox, or a support staff accidentally archived it thinking the forum had been replied to. If you ever have a delay, please by all means email us directly at support. You should never have to even wait a day for a reply, we try and be very responsive. We don't intentionally leave someone waiting. So I apologize.

To answer your questions...

HA needs two licenses, correct.

Its expected you will have a shared network server, a SAN, or windows file server, etc. Something common the data would be getting stored on.

There are ways CrushFTP can do dual write to write data in multiple places, but this isn't ideal for HA as if the opposite side is down, the VFS in crush becomes read only since it can't guarantee the data is written, and it doesn't do journals to change it later when it is available.

Hope this helps. Again, sorry or the delay.

Thanks,
Ben
Can you send us an email directly to support and give us a test account so we can login and get this error ourselves so we know what is going one exactly?

Thanks,
Ben
Sorry, the logging format won't be changing. Apache does HTTP.

CrushFTP does HTTP, reverse proxy, Socks, HTTP proxy, FTP, FTPES, FTPS, SCP SFTP, SSH tunnel, HTTP Tunnel, Jobs...each of which does there own infinite possibility of complex actions, and other dumps they can do, etc... We can't try and match an old tool that frankly, has terrible logs that don't provide enough info to debug an issue should one really occur. Just my opinion of Apache styled logs. We couldn't achieve the goal if we wanted to, but we also don't want to because we only see downsides in trying to achieve it.

As for filtering items out, you can do this in the prefs, logging, you can filter patterns away from logs. *192.168.5.2* for example would remove any log entry containing that IP.

Thanks,
Ben
Start the template with <html><body> and end with </body></html>

Make sure your prefs, general, smtp is set to use html as well.

Thanks,
Ben
Do you know what the name was previously so we can try and debug the issue here?
Maybe its the web browser being used?

Or the name you gave the email template? What name did you use on the template?

Thanks,
Ben
How do you know its not?

What is showing in the CrushFTP.log file?

Thanks,
Ben
But it won't matter also until you upgrade to 7.1. Your on an older build, granted you didn't know, but we just released 7.1 yesterday. Your copy will notify you within 7 days. But upgrade first now to see if you still have an issue, then get the log samples to send to us.

--Ben
I deleted your post. Do not post the log snippet here.

zip it, and email it to us directly.

Thanks,
Ben
You can use the keywords column to hold extra data...but no other columns are possible.

Thanks,
Ben
What exact CrushFTP version is this?

The CrushFTP.log is what you need to trace exactly what went on. And you may need the prefs, logging, debug level set to 1 as well.

Thanks,
Ben
 
Forum Index » Profile for spinkb » Messages posted by spinkb
Go to:   
Powered by JForum 2.1.8 © JForum Team