Is there a specific reason why SeaFile version is so old (it's 6.3.4 from 2018, whereas the latest is 11.0.9)?

Alternatively, did anyone successfully migrate existing data to latest?

On 7/9/2024 at 1:40 PM, bgr said:

Is there a specific reason why SeaFile version is so old (it's 6.3.4 from 2018, whereas the latest is 11.0.9)?

Alternatively, did anyone successfully migrate existing data to latest?

Going to nudge this also. I generally hate nudging but this seems to have been asked a few times.

 

This definitely taught me to research repositories and when they were last updated (my bad for not checking, lesson learned!). But now I have several people using my Seafile with about 3TB stored and more coming in every day. I would love to migrate to the current version but don't want to make it a bad experience for all involved. Would hate to have to help family members through any resyncing issues or data loss.

Is the SeaFile template correct?  I didn't see a volume/path to store user data versus the configuration path.

My apologies for such a nooby question.  I know how to code PHP and HTML but am unfamiliar with the full setup needed to get PHP working.  I am just trying to get an internal webpage to use as a PHP sandbox.  I have installed your docker and placed my index HTML/PHP file in nginxphp8\www\index.php. I was thinking this docker already had PHP installed on it.  If i rename my file to 'Index.html' then the web gui works but if i change it back to 'index.php' it doesn't.  Am i missing something simple here?  

I keep getting incorrect username and password.

I spent WAY too much time on this....

I tried changing it on the DB directly, deploy with default account, nothing works 😞

On 9/27/2024 at 9:22 PM, 8BitMercy said:

Going to nudge this also. I generally hate nudging but this seems to have been asked a few times.

 

This definitely taught me to research repositories and when they were last updated (my bad for not checking, lesson learned!). But now I have several people using my Seafile with about 3TB stored and more coming in every day. I would love to migrate to the current version but don't want to make it a bad experience for all involved. Would hate to have to help family members through any resyncing issues or data loss.

 

On 11/12/2024 at 4:49 PM, Jaybau said:

Is the SeaFile template correct?  I didn't see a volume/path to store user data versus the configuration path.

 

I am also interested in this.

I just looked at this and spend more time than I care to admit setting up reverse proxy with SWAG only to then notice the version and wanted to move the stored files directory as looking at the template it is pointing /shared to appdata. But looking in the advanced admin settings I can see more options so reluctant to tinker until the version is resolved. Any update on this?

It would be nice if someone made a new Docker for this project. This specific one is woefully outdated and the other two do not include MariaDB or Memcached so you need to download other apps to get it to run, not to mention the other random things they have written in their instructions.

 

Edited January 22, 20251 yr by Tyestor

I'm using the template NginxProxyManager-CrowdSec by lepresidente ... looking for help with the Crowdsec bouncer not enabling, and haven't had any luck on their Github or Reddit ... wondering if someone here can help.

 

I'm looking for help getting this error corrected. I believe I have the crowdsec-openresty-bouncer.conf setup correctly.

nginx: [error] [lua] config.lua:124: loadConfig(): unsupported configuration 'ENABLE_INTERNAL' 
nginx: [alert] [lua] crowdsec_openresty.conf:5):9: [Crowdsec] Bouncer Disabled

I believe I have the rest of the crowdsec processing NPM logs correctly.

ENABLED=true API_URL=http://CROWDSECIP:8082 API_KEY=key-from-crowdsec

I can ping CROWDSECIP from the NPM container as well.

The crowdsec bouncer hasn't seen NPM trying to connect yet:

───────────────────────────────────────────────────────────────────────
 Name       IP Address  Valid  Last API pull  Type  Version  Auth Type 
───────────────────────────────────────────────────────────────────────
 npm-proxy              ✔️                                   api-key   
───────────────────────────────────────────────────────────────────────

 

how do you change the default page on ngenix on nraid

On 3/7/2025 at 2:59 PM, rynh said:

I'm using the template NginxProxyManager-CrowdSec by lepresidente ... looking for help with the Crowdsec bouncer not enabling, and haven't had any luck on their Github or Reddit ... wondering if someone here can help.

 

I'm looking for help getting this error corrected. I believe I have the crowdsec-openresty-bouncer.conf setup correctly.

nginx: [error] [lua] config.lua:124: loadConfig(): unsupported configuration 'ENABLE_INTERNAL' 
nginx: [alert] [lua] crowdsec_openresty.conf:5):9: [Crowdsec] Bouncer Disabled

I believe I have the rest of the crowdsec processing NPM logs correctly.

ENABLED=true API_URL=http://CROWDSECIP:8082 API_KEY=key-from-crowdsec

I can ping CROWDSECIP from the NPM container as well.

The crowdsec bouncer hasn't seen NPM trying to connect yet:

───────────────────────────────────────────────────────────────────────
 Name       IP Address  Valid  Last API pull  Type  Version  Auth Type 
───────────────────────────────────────────────────────────────────────
 npm-proxy              ✔️                                   api-key   
───────────────────────────────────────────────────────────────────────

 

Have you found a solution in the meantime? I'm facing the same problem... thank you very much.