Author Topic: https://192.168.10.42:444 does not work  (Read 1840 times)

Offline sboyce

  • Newbie
  • *
  • Posts: 4
https://192.168.10.42:444 does not work
« on: January 05, 2013, 06:48:00 PM »
I thought apache may have been needed so I installed it but that didn't make a difference.
Is there a different web server needed?
# tail -50 /var/log/apache2/
access.log               error.log                other_vhosts_access.log 
root@raspberrypi:/usr/src/firehol-1.273# tail -50 /var/log/apache2/access.log
192.168.10.2 - - [21/Dec/2012:11:21:46 +0000] "GET / HTTP/1.1" 200 483 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0"
192.168.10.2 - - [21/Dec/2012:11:21:46 +0000] "GET /favicon.ico HTTP/1.1" 404 502 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0"
192.168.10.2 - - [21/Dec/2012:11:21:47 +0000] "GET /favicon.ico HTTP/1.1" 404 502 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0"
root@raspberrypi:/usr/src# tail -50 /var/log/apache2/error.log
[Fri Dec 21 11:13:37 2012] [notice] Apache/2.2.22 (Debian) configured -- resuming normal operations
[Fri Dec 21 11:21:46 2012] [error] [client 192.168.10.2] File does not exist: /var/www/favicon.ico
[Fri Dec 21 11:21:47 2012] [error] [client 192.168.10.2] File does not exist: /var/www/favicon.ico
root@raspberrypi:/usr/src/firehol-1.273# ls /var/www/
index.html

Offline Arne.F

  • Administrator
  • Master Supporter
  • *****
  • Posts: 5,612
Re: https://192.168.10.42:444 does not work
« Reply #1 on: January 05, 2013, 07:53:31 PM »
You don't need Apache on the host to reach the IPFire WebIF. (IPFire brings it own)

But fully explain what you try to do.
« Last Edit: January 05, 2013, 07:56:42 PM by Arne.F »
Arne

Support the project on the IPFire whishlist!






Offline sboyce

  • Newbie
  • *
  • Posts: 4
Re: https://192.168.10.42:444 does not work
« Reply #2 on: January 05, 2013, 08:59:07 PM »
You don't need Apache on the host to reach the IPFire WebIF. (IPFire brings it own)

But fully explain what you try to do.
Simply "https://192.168.10.42:444". I can't connect.

I can ssh into it from other Linux boxes on the LAN.

Do I need to set up a firewall rule before I do this?

I downloaded the Raspberry Pi IPFire and burned it on to a SD card so it does not come up with configuration screens you get with a CD install.
Image used ipfire-2.11.2gb-ext2.armv5tel-full-core65.img
« Last Edit: January 05, 2013, 09:54:21 PM by sboyce »

Offline Arne.F

  • Administrator
  • Master Supporter
  • *****
  • Posts: 5,612
Re: https://192.168.10.42:444 does not work
« Reply #3 on: January 06, 2013, 03:16:57 PM »
You have downloadad a Marvell kirkwood only image.

Quote
I can ssh into it from other Linux boxes on the LAN.
Sure that you have connected the correct system or you have not written it to the sd-card. There is no 2.11-core65 image for raspberry pi.

There are only a few testimges of IPFire 2.11 (core62) in my own area and the new 2.13Beta1 what is the first official image that support Raspberry Pi.

http://downloads.ipfire.org/release/55
Select arm and the image without serial console.
« Last Edit: January 06, 2013, 03:22:07 PM by Arne.F »
Arne

Support the project on the IPFire whishlist!






Offline sboyce

  • Newbie
  • *
  • Posts: 4
Re: https://192.168.10.42:444 does not work
« Reply #4 on: January 06, 2013, 04:05:02 PM »
I downloaded 2.11 on 23rd. Dec.
I'll try 2.13.

Offline sboyce

  • Newbie
  • *
  • Posts: 4
Re: https://192.168.10.42:444 does not work
« Reply #5 on: January 06, 2013, 11:21:52 PM »
Installed ipfire-2.13beta1.1gb-ext4.armv5tel-full-core65.img and it's up and running.
Thanks for the help.