GEDCOM file that is 25mb

[dennis800121]

Hi!

I have TNG 15.0.3 installed on my own server, running PHP 8.4.16 and MySQL 11.4.10. I’ve been trying to import a GEDCOM file that is around 25 MB, but nothing happens. The progress bar just stays still. The file is located on the server in TNG’s GEDCOM folder. I know the GEDCOM file is valid because it works in other genealogy programs. I also haven’t had any issues with other GEDCOM files before.

What can I do to fix this?

[Chris Lloyd]

Use an FTP program to upload it

[Philip Roy]

6 hours ago, dennis800121 said:

The file is located on the server in TNG’s GEDCOM folder

It already has been uploaded from what the original post says.

Do you know what version the GEDCOM file is? And I believe you can now have files that include images I think…does your file have those? If so, try a version that excludes images and upload those separately.

How many people exist in the GEDCOM you’re using?

[dennis800121]

7 hours ago, Philip Roy said:

It already has been uploaded from what the original post says.

Do you know what version the GEDCOM file is? And I believe you can now have files that include images I think…does your file have those? If so, try a version that excludes images and upload those separately.

How many people exist in the GEDCOM you’re using?

The GEDCOM file is version 5.1 and contains approximately 100,000 individuals.
Example from the beginning:
 

0 HEAD
1 SOUR xxxxxxxxxx
2 VERS 1.0
2 NAME xxxxxxxxxx
1 DEST TNG
1 DATE 13 JUN 2026
1 CHAR UTF-8
1 GEDC
2 VERS 5.5.1
2 FORM xxxxxxxxxx
1 SUBM @SUBM1@
0 @SUBM1@ SUBM
1 NAME xxxxxxxxxxt
0 @S6@ SOUR
1 TITL Strövelstorps kyrkoarkiv, Födelse- och dopböcker, 798160 (1661)
0 @S10@ SOUR
1 TITL Kågeröds kyrkoarkiv, Födelse- och dopböcker, 9935 (1690-1759)
0 @S12@ SOUR
1 TITL Allerums kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13003/C I/1 (1690-1749)
0 @S13@ SOUR
1 TITL Allerums kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13003/C I/2 (1750-1799)
0 @S14@ SOUR
1 TITL Allerums kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13003/C I/3 (1800-1836)
0 @S19@ SOUR
1 TITL Allerums kyrkoarkiv, Vigselböcker, SE/LLA/13003/E I/1 (1830-1842)
0 @S21@ SOUR
1 TITL Allerums kyrkoarkiv, Vigselböcker, SE/LLA/13003/E I/3 (1857-1873)
0 @S25@ SOUR
1 TITL Anderslövs kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13004/C I/1 (1757-1854)
0 @S31@ SOUR
1 TITL Andrarums kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13005/C I/2 (1721-1734)
0 @S35@ SOUR
1 TITL Ausås kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13015/C I/3 (1756-1805)
0 @S39@ SOUR
1 TITL Baras kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13019/C I/1 (1719-1794)
0 @S40@ SOUR
1 TITL Baras kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13019/C I/2 (1795-1837)
0 @S41@ SOUR
1 TITL Baras kyrkoarkiv, Födelse- och dopböcker, SE/LLA/13019/C I/4 (1838-1861)

 

[ajnsmits]

Maybe you could try this: 

[Rob Severijns]

Also have a look at:

    php_value upload_max_filesize
    php_value post_max_size
    php_value memory_limit
    php_value max_execution_time

Usualy in htaccess
 

[dennis800121]

Hi!

Thanks for the suggestions!
I’m running Nginx (TNG is hosted locally on my Unraid server and exposed to the internet), and as far as I understand, I’m supposed to add the settings to php-local.ini.

date.timezone = Europe/Berlin
upload_max_filesize = 100M
post_max_size = 100M
memory_limit = 1024M
max_execution_time = 600

But it still doesn’t work!

[Rob Severijns]

That's even better.

Beter choice for security/privacy/speed:
Nginx = faster, better for handling many requests, good reverse proxy, cleaner security headers.
.htaccess = Apache-specific, easier if you only have shared hosting, but slower because Apache checks .htaccess files per request.

Not sure why it still doesn't work.