XF 2.0 Xenforo 1.5 -> 2.0 Upgrade Issues

Hizen

Member
Hello! I am having issues upgrading XenForo 1.5

I am in the process of moving host, and I also want to upgrade at the same time. My old board (still running) is located at https://forum.blackout-ro.net, while my new board is http://165.227.9.227/forum/ (the latter will become the former once the move is finished).

To move, I did the following things.
  • Backup both the XenForo (forum) directory and the SQL database.
  • Move both to the new host using SFTP.
  • Download 2.0 upgrade -> Upload to server -> Unzip and overwrite.
  • chmod 0777 on data and internal_data folders.
Despite doing the chmod, I'm still being asked to do so.
tqOzPiK.png


As you can see, the folders definitely have world writable permissions.
bJBSxRm.png


Help is appreciated. Thank you. :)
 
Last edited:
I did not have to chmod anything...
on my server, it is auto set to 644 on upload...
(and I had no issues....)

and it really depends on what permission
your server uses, not all servers use 777...
not all servers are equal....

on my server, folders are 755, and
files are normally set for 644....
 
Are the data and internal_data directories owned by apache too?
yes.

For reference, I'm using CentOS 7.4 and it's fresh, only with the minimum requirements installed (apache, php [PHP 5.4.16] +dependencies [dom, xml, gd, bcmath, mysql], mariadb, some other stuff such as git, nano and zip)

I tried downloading XenForo 2.0.1 the full package, not just the upgrade, and now I'm getting this:
1516772364002.webp

I swear on me nan's life I have done what it asks. /var/www/html/forum is now owned by my user, as it was the one who uploaded the files. My /var/www/html directory is untouched except I did sudo chmod 777 /var/www/html so I could upload files.
 
Last edited:
Let it be know that this error was caused by the monster named SELinux...i had to disable it to get around this. I don't know how it affects the system, hopefully nothing bad...

https://blog.lysender.com/2015/07/c...pache-cannot-writeaccess-file-no-matter-what/

Hoping support people can read these comments and hopefully understand future issues like mine. Also, is there a better option than disabling SElinux? :|
 
Last edited:
Let it be know that this error was caused by the monster named SELinux...i had to disable it to get around this. I don't know how it affects the system, hopefully nothing bad...

https://blog.lysender.com/2015/07/c...pache-cannot-writeaccess-file-no-matter-what/

Hoping support people can read these comments and hopefully understand future issues like mine. Also, is there a better option than disabling SElinux? :|


There are a few possible solutions to keep SELinux enabled mentioned on this page : https://unix.stackexchange.com/questions/50639/httpd-cant-write-to-folder-file-because-of-selinux
 
Let it be know that this error was caused by the monster named SELinux...i had to disable it to get around this. I don't know how it affects the system, hopefully nothing bad...

https://blog.lysender.com/2015/07/c...pache-cannot-writeaccess-file-no-matter-what/

Hoping support people can read these comments and hopefully understand future issues like mine. Also, is there a better option than disabling SElinux? :|

Yep, you got it! If you'd prefer to not disable SELinux, try the following as it should get you past this hurdle.

Bash:
sudo semanage fcontext -a -t httpd_sys_rw_content_t '/your/path/to/xenforo/data(/.*)?'
sudo semanage fcontext -a -t httpd_sys_rw_content_t '/your/path/to/xenforo/internal_data(/.*)?'
sudo restorecon -Rv '/your/path/to/xenforo/'

If you'd like to verify your changes, try the command
Bash:
ls -Z
 
Back
Top Bottom