Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ryanbrown]

I have a DNS-323 and running the Apache Webserver on a computer that is connected to the DNS-323 through a DIR-655 Router. I am able to successfully configure the Apache Server to host the Document Root (website) on my DNS-323, however, the DNS-323 requires a "login" when the website is accessed by the Apache server so I get the message "The website declined to show this webpage".

My question, can I configure the DNS-323 to accept access request from the Apache server OR can I add something to the document root address that "enters" the login automatically?

So, currently my document root in Apache is "//dlink_nas/volume_1/my_website". When you try to access that folder is when I get the message "The website declined to show this webpage".

Anyone have any ideas or any other configurations to allow me to keep my website on the DNS-323?

[fordem]

You should be able to configure the DNS-323 for - let's call it "open access" - where no login or password is required, in fact this is the default unless you changed it.

[ryanbrown]

Then that would tend to indicate that you could enable the DNS-323 to be accessed from outside the network (via http) without being logged in but that is not how it is working.

Let's say I forward port 80 on my DIR 655 router to the address of the DNS-323. When I type in my external ip address with :80 on the end, I get my DNS-323 web configuration page instead of the drive itself.

----

So, if I have a program on my computer in my network that tries to automatically attach to a folder in the DNS-323 and display its contents in a webpage, why would I still get the "webpage not accessible" message in IE?

Has anyone set up the DNS-323 as their websever / webpage file storage that could give me their general configuration / setup?

[fordem]

Maybe I am missing something here - is the Apache server on the same LAN as the DNS-323?
 - if it is, then you will not be accessing the DNS-323 from outside the network.
 - if it's not, then I don't see the point in what you're trying to do.

You seem to be missing a couple of key concepts - http is not a protocol normally used to access stored files - and at least with the current firmware (1.06), you cannot access data on the DNS-323 that way, you have to use either ftp or CIFS/SMB.

So - if you have a program on a computer in your network that tries to automatically attach to a folder in the DNS-323 and display it's contents in a webpage - you would NOT be accessing the DNS-323 via it's web interface, but via, most likely CIFS/SMB (this will be determined by the program).

It is not uncommon to have a web server access other local servers for content to go into a webpage - it may be unusual to do it with low end gear like the DNS-323, but it is one of the building blocks in e-commerce installations, a so called "n-tier server architecture" where the webserver is the first tier and merely serves the webpages, the content of the page is generated by an application server (second tier) and there is a database server hosting SQL databases forming a third tier - and - when I say the webserver is the first tier, that first tier could actually be a few dozen servers, linking to multiple application servers in the second tier and then a cluster server for the database backend.

[ryanbrown]

Hmmmm..OK, It is probably best if I tell you what I am trying to do instead of just asking the individual questions. So here's the deal....

I signed up at DYNDNS for a free web address that will forward to my home IP address anytime someone types my address in their browser just as any other webpage. For the purposes of this explanation, let's just say my address is www.mywebpage.dyndns.org.

I have a Dlink DSL modem (dsl2320b), a Dlink router (dir655), a DNS-323 and 3 computers all "hooked" together. So I forward port 80 to 1 of my computers that has the Apache server. (This is an older computer that I don't use regularly.) I have the Apache server receive the HTTP request and "get" the webpage from a folder on my DNS-323. I'm not talking files, like in FTP or something but rather I have a full website stored in a file on the DNS-323.

So, all is good, except that when I goto to my browser to see if my website works, I type in www.mywebpage.dyndns.org and get the following error " This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage."

I can't figure out why this doesn't work........I agree it would be slow but we are talking about a simple home webpage for some pictures of the baby and a few words about the family. Nothing much.

OK, so, what you think?

Thanks in advance for working with me on this...

[ryanbrown]

Wait a seond guys....this isn't a DNS-323 access problem. I just transfered the site over to my local drive and changed the document root....same problem.

This is something else. Sorry guys. Thanks anyway. Back to the drawing board!

[fordem]

Just a comment - most web sites aren't that large, in terms of file size - it would probably be a lot easier to leave the whole kit and kaboodle on the box running Apache.

[ryanbrown]

It's working!

Once I started looking elsewhere for the problem, I found that I need to change the directory root as well as the document root. All is running smoothly with no issues.

I agree with you fordem. This one is smaller than even the average. However, my reasoning for running it seperately is just that I have an older laptop that I am using as my always on webserver but I actually create, edit and update the webpage from my newer laptop. Hence the ease of access to having the website located on the DNS-323.

Since the webserver needs a fixed IP, LAN connected and so forth to work at its best, this is easier and gives me the freedom of being more mobile with my primary laptop.

I am interested in hosting all on the DNS and will look further into your suggestion. I realize it is a lower end piece of equipment in the grand scheme of things but I'll eventually squeeze every "bit" it's got in its little heart out.

Thanks to all - sorry for the goose chase.....

[madpenguin]

Why not run your web site straight from the NAS instead?

Doesn't make a whole lot of sense having 2 machines running when just the NAS can do it. You can still map Volume_1 in windows and make your changes the same way your doing now. Less electricity that way.

I'm using dyndns as well. This is on my 323 in the closet:

http://www.jaguarlinux.com/

php, mysql, postfix/sendmail... You name it, you can do it native on the 323. Would probably run faster than apache on your current box.

[garyhgaryh]

madpenguin: nice site!

[fordem]

Ryan

This is not about where you create the website, in most cases, websites are created on one platform and hosted on another - the websites I have worked on were created on a laptop or desktop in my home, and the servers hosting them are several thousand miles away.  I use ftp to upload the files to the servers.

Personally I think that storing the site on the same hardware on which it is hosted (whether that be the laptop or the DNS-323) would be simpler.

[mirceani]

Question for Madpenguin

Can you please help and explain how can you host the Apache webserver on the DNS-323 ?

Thank you

[D-Link Multimedia]

Question for Madpenguin

Can you please help and explain how can you host the Apache webserver on the DNS-323 ?

Thank you

As long as its in a PM or on another forum....

[madpenguin]

Question for Madpenguin

Can you please help and explain how can you host the Apache webserver on the DNS-323 ?

Thank you

I know it's old but someone just pm'ed me about this thread. So answer the question above, why would you want to? Apache is a beast that would slow the 323 down to the point of unusability. Have to remember it's a small ARM processor with a tiny bit of memory. lighttpd is the way to go with this box.