Interworx 6 to Interworx 7 Upgrade?

[bear]

Morning John
Thank you for the explanation.
Enjoy the rest of your weekend
thanks again

[IWorx-Jenna]

IW7 went live early 2020. So for the last almost-two-years (since, oh my gosh I can’t believe 2021 is almost done), if folks wanted to use IW7, we advised them to install on a new server, and use the mass import tool to migrate their SiteWorx accounts from their IW6 to IW7 server.

So, no, you should not run into any issues, since that is what people have been doing for almost two years, now. However, the same caveats as the upgrade exist, in that the vhost system is a little different, so you should check for any customization, first.

[IWorx-Jenna]

Re graphs: that’s a known bug in IW7–there is no way to really access other views right now, other than put the whole path manually in the URL. So, for instance, if you add /nodeworx/rrd?action=historyCommit&service=memory&graph=usage, you’ll see all the views for the memory graphs, but that is a pain.

I’ll bump the ticket with the devs, though no ETA.

Re the permission on the index.html file, 755 has been a standard for new accounts for quite some time. It is that way for new accounts on IW6, as well. Example:

[root@permcheck ~]# rpm -q interworx
interworx-6.11.3-1936.iworx.noarch
[root@permcheck ~]# ls -la /home/novoneth/nov13account.com/html/
total 92
drwx--s--x 2 novoneth novoneth    24 Nov 13 11:28 .
drwx--s--x 4 novoneth novoneth    38 Nov 13 11:28 ..
-rwxr-xr-x 1 novoneth novoneth 93125 Nov 13 11:28 index.html
[root@permcheck ~]#

I vaguely remember a discussion from a few years ago where there was a reason for that, but I can’t remember off the top of my head what that reason might have been.

[iworx-brandon]

@d2d4j

I do have a question though, which I maybe overthinking - could a user change SSL ciphers by adding their own .conf in the users apache folder

If so, I believe this has the potential to stop apache restarting of not 100% correct and if so, how easy would it be to track down the potential user causing the conflict in SSL

Good question: the user doesn’t have the ability to write to this folder unless you’ve somehow granted them iworx/root level privileges and if you’ve done that, Apache not restarting is likely the least of your worries. Ha ha.

I suppose it would be possible for a SysAdmin to write something like that in there and cause a headache for themselves, but if we were to provide a feature that prevents SysAdmins from doing weird things like this, we’d likely have to charge a whole lot more per-license.

[d2d4j]

@iworx-brandon

Good question: the user doesn’t have the ability to write to this folder unless you’ve somehow granted them iworx/root level privileges and if you’ve done that, Apache not restarting is likely the least of your worries. Ha ha

Hi @iworx-brandon haha very good thank you but years (IW 5 to early I think IW 6) ago users via FTP and if allowed, SSH did have full access to /var but file manager from IW-CP did not.

However, there were no apache folder back then (only appeared last year or 2 or so) so this is a change I was not aware off and naturally thought it was still in place.

Glad it is not then as it is an easy way to make changes without changing the vhost.

Many thanks

John

[d2d4j]

Hi

Sorry I meant to also mention before the introduction of the SSL ciphers into IW-CP late 5 onwards, it was normal to make changes both in httpd.conf and vhost for ciphers

There were plenty of forum posts from a lot of users including myself.

Here is an event hook written by Iworx-Mat

Custom SSL CipherSuite - Customization / Hacks / Tools / Tips / Tricks - Interworx Forum

When the IW ciphers were added to nodeworx, it made it simpler and easier

Many thanks

John

[Justec]

Did the upgrade today and not only did it go perfectly smooth, it only took about 3 mins to run.

Well done InterWorx team!!

[IWorx-Jenna]

Glad it worked well for you!