vBulleting / Ubuntu

Hi all,

Hoping someone with far greater knowledge than me can help with a problem I am having...i got a bit bored and decided to challenge myself.

The challenge?

Boot up a Ubuntu VM and setup a vbulletin forum.

So I did all the initial setup stuff following the guide on the vbulletin website, managed to run the install.php file and did all the base setup stuff, however the problem is when trying to load up the homepage of the forum I get a page with no images / formatting and an error that says The requested URL *forumname*/auth/login-form was not found on this server.

I've googled and nothing seems to work, so just wondering if anyone on here could maybe point me in the right direction?

Thanks

Could be a permissions issue or it could be networking. Does it work using a browser on the same VM using localhost as the address. I guess you have got apache working OK?

Is it a 404 not found error or some message from the forum software?

If it's a 404, check the apache (I'm guessing it's apache not nginx or something) logs. Can you link to the instructions you used otherwise it's the blind leading the blind!

Can you screenshot the actual error you're seeing?

What web server are you using (Apache, nginx,etc?), sounds like a routing issue.

Been a while since I've used vBulletin, but can you turn off "pretty" urls, see if it makes a difference?

Peter - I should have said, I am trying to access it from the vm localhost/forumname is the link to the forum I am using.

I am indeed using Apache - as for the error I can't remember the full error, will get it when I get home this evening.

These are the instructions I used for installing vBulletin - Instructions

I know the DB is there as I've tested and I know apache is running as if I go to just localhost then I get the default apache page

Not installed v-bulletin myself - so Im probably not the best person to take this further - but might be worth checking the permissions on the relevant homepage files and and stylesheets.

This thread on vBulletin.com sounds like it's the issue you are having (albeit with the OP there running it on Windows).

If the .htaccess is in place with the expected entries for prettifying the URL, then it may be that you still need to edit Apache's http.conf as they did.

Quote:

---

SOLVED, i had to think to:
open my http.conf and ... un-comment for apache
LoadModule rewrite_module modules/mod_rewrite.so
so after apache restart all work like a charm ... just because the .htaccess now is processed! thank you!

---

Quote:

---

Originally Posted by Output

This thread on vBulletin.com sounds like it's the issue you are having (albeit with the OP there running it on Windows).

If the .htaccess is in place with the expected entries for prettifying the URL, then it may be that you still need to edit Apache's http.conf as they did.

---

Cheers, tried this but Ubuntu doesn't have a http.conf file and the equivalent it used to have, it not longer has (According to some googling)

I've done that much tinkering I've forgotten where I'm up to and what I've tried.

I think ill recreate the vm and start again, this time hopefully the extra bit of knowledge I have will help :)

This might help

https://httpd.apache.org/docs/2.4/configuring.html

It does state that there is a http.conf file, the location can vary though - if you compile it yourself from the source you have finer control. Using pre-compiled binaries for a given distro is easier, but you lose that control.

Quote:

---

Originally Posted by Disturbedguy

Cheers, tried this but Ubuntu doesn't have a http.conf file and the equivalent it used to have, it not longer has (According to some googling)

I've done that much tinkering I've forgotten where I'm up to and what I've tried.

I think ill recreate the vm and start again, this time hopefully the extra bit of knowledge I have will help :)

---

It appears that the options may now be located in the /etc/apache2/conf-available or /etc/apache2/mods-available directories according to https://help.ubuntu.com/lts/servergu...-configuration.

Either way, I wish you the best of luck getting it figured out. :)

I'd also recommend if you are starting a fresh VM, try out nginx instead of Apache.

Quote:

---

Originally Posted by peterb

This might help

https://httpd.apache.org/docs/2.4/configuring.html

It does state that there is a http.conf file, the location can vary though - if you compile it yourself from the source you have finer control. Using pre-compiled binaries for a given distro is easier, but you lose that control.

---

You don't lose control using pre-compiled binaries, you do gain all the advantages of a proper package management system.

On my old Centos box if I didn't know where the httpd.conf was, knowing one file involved (like the init script to start it) is all you need to ask the package manager "which package does this file belong to":

$ rpm -q -f /etc/rc.d/init.d/httpd
httpd-2.2.15-60.el6.centos.4.x86_64

From there you can list the contents of the package, possibly grepping for the answer if you are after something specific:

$ rpm -q -l httpd | grep conf
/etc/httpd/conf
/etc/httpd/conf.d
/etc/httpd/conf.d/README
/etc/httpd/conf.d/welcome.conf
/etc/httpd/conf/httpd.conf
/etc/httpd/conf/magic
/etc/sysconfig/htcacheclean
/etc/sysconfig/httpd
/usr/lib64/httpd/modules/mod_log_config.so

If you compile something from source, you lose all this sort of stuff.

Quote:

---

Originally Posted by DanceswithUnix

You don't lose control using pre-compiled binaries, you do gain all the advantages of a proper package management system.

---

I did say finer control :). But yes, there are pros and cons to both approaches. Compiling means you can get the latest versions as soon as they are available and if its an older distro where packages are no longer updated, that may be only way to get them. And you can compile them and make your own package for the package manager (if you really want to :) ). But I agree, pre-compiled binaries are much simpler.

Horses for courses.