I have content on a network drive that I can only access over VPN. The security profile for the VPN requires that I reauthenticate every 8 hours. Unfortunately the content on the drive is large enough that it needs more than 8 hours to index.
I am not indexing the entire network share, only a sub folder. So instead of enabling the network share in Options->Indexes->Network Drives, I put the path in Options->Indexes->Folders.
When the VPN disconnects, it seems that any files remaining on the queue for indexing get dropped? /rescan doesn't seem to get those dropped files back on the queue.
Is there a way to recover from a disconnected VPN so that files that do not have their content indexed are retried?
Thank you, this is a great tool.
Content Index and VPN disconnection
Re: Content Index and VPN disconnection
Thank you for your feedback.
I will look into improving disconnection detection.
-Everything does has some offline detection. However, this is limited to local disks.
For now, please search for:
where j: is your network drive.
-This searches for files missing content.
Select all files and press Ctrl + F5.
-This will refresh indexed properties and content.
Another option is to preemptively pause property indexing and reconnect your VPN:
I will look into improving disconnection detection.
-Everything does has some offline detection. However, this is limited to local disks.
For now, please search for:
j: file !content:where j: is your network drive.
-This searches for files missing content.
Select all files and press Ctrl + F5.
-This will refresh indexed properties and content.
Another option is to preemptively pause property indexing and reconnect your VPN:
- From the Index menu, click Pause Property Indexing.
- Reconnect your VPN
- From the Index menu, click Update Indexed Properties.
-
flyingrobots
- Posts: 4
- Joined: Tue Jun 03, 2025 12:06 pm
Re: Content Index and VPN disconnection
I'm not so much worried about disconnection detection, I've seen for myself how challenging it can be for network related connections. The fact that Everything doesn't just choke when the network goes down shows the incredible job you've done with it. It is extremely robust.
Knowing how I can restart the content indexing was the main thing I was looking for, and the fact it exists is just another proof on how well this has been thought out.
Don't mean to sound over the top, but I sincerely love what you've done here.
Thank you
Knowing how I can restart the content indexing was the main thing I was looking for, and the fact it exists is just another proof on how well this has been thought out.
Don't mean to sound over the top, but I sincerely love what you've done here.
Thank you
-
flyingrobots
- Posts: 4
- Joined: Tue Jun 03, 2025 12:06 pm
Re: Content Index and VPN disconnection
Code: Select all
j: file !content:However, I select the files and press ctl-F5 and nothing seems to happen. Nothing in the status bar and I don't see any updates to the Tool->Options->Indexes->Content property page doesn't show the current file it is indexing (which it did when I first ran index on the folder.
Thanks
-
flyingrobots
- Posts: 4
- Joined: Tue Jun 03, 2025 12:06 pm
Re: Content Index and VPN disconnection
I don't seen Everything responding to the above. I am currently connected to the VPN and went through the steps of pausing property indexing and then update indexed properties, but it didn't appear that Everything restarted indexing.Another option is to preemptively pause property indexing and reconnect your VPN:
From the Index menu, click Pause Property Indexing.
Reconnect your VPN
From the Index menu, click Update Indexed Properties.
Re: Content Index and VPN disconnection
Everything should show a progress bar on the right of the status bar.
The progress bar might not appear if you are only reindexing a few files.
Please try capturing a debug log:
The progress bar might not appear if you are only reindexing a few files.
Please try capturing a debug log:
- In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging...
- Search for:
j: file !content:
(where j: is your network drive.) - Select all files (Ctrl + A)
- Press Ctrl + F5.
---Let Everything sit for a minute. - From the Tools menu, under the Debug submenu, click Stop Debug Logging...
---This will open your %TEMP%\Everything Debug Log.txt in Notepad. - Please upload this file in a bug report