Jump to content

Lopburi99

Advanced Member
  • Posts

    1,293
  • Joined

  • Last visited

Posts posted by Lopburi99

  1. Worked like a charm all last night, now this morning won't work at all. Port 80 sometimes open, sometimes closed. Wherever the switching is taking place, it is inconsistent.

    BTW, I am well aware what a stupid IP address is, I was referring to the final 1 in 192.168.1.1 as a port #, similar to 192.168.1.99 corresponding to my static port 99, sorry if that was too subtle. But please, go ahead and continue your ego-serving food fight without me. (Gotta love the TV ignore feature). I've been successfully configuring and operating Pi and Beaglebone applications, including evaluating the popular web servers, for over a year. Currently I am trying to conclude if I prefer Apache2 over Lighttpd or Nginx for various usage scenarios I have in mind. I've been self-employed IT for 42 years. I don't need to defend my credentials to anybody.

  2. You need to have a service running on your computer that has the ports open locally plus port forwarded from the router to the local computer for it to detect it. Plus, the firewall on the PC needs to be set to allow incoming connections on 80/443.

    I run an Apache server and if I stop the service 443 shows closed. Restart the service 443 shows open. Port 80 shows closed in either case.

    Exactly.

    Without running services on these ports, they show closed.

    This was my situation. Didn't know my server had to be running on the Pi for port 80 to be shown as open. Others take note. Thanks guys.

  3. I temporarily switched off my windows firewall, started my Apache2 server, checked port 443. Still closed. Maybe allowing opening 443 is a "feature" of the 950 Baht plan? Still waiting what 3BB has to say about all this.

    When you run netstat -a from cmd window (if running Windows, else sudo netstat -a for linux) does it show 80/443 Listening?

    It shows 80 listening, no mention of 443, but says 445 is listening.

    Huh? Now portcheck shows 80 open? Maybe 3BB is looking into this as we speak.

  4. I went through this recently with 3BB when I setup a private cloud at home. Spent a lot of time investigating it and 3BB indeed blocks incoming 80 but 443 (SSL) was open and since I wanted my cloud access secure anyway it worked out for me. But, as mentioned, many ISPs will block incoming port 80 to prevent home users setting up a website as they are suspicious it may be commercial and cut into the traffic. Since I do not have a static IP, I use No-Ip and port forwarded on my router port 443 to my apache server. Port 80 (3BB) shows closed on all websites that have port scanners to test for open ports but 443 ok.

    is your port 443 also open from abroad?

    Yes, as I used several online port scanners from outside of Thailand to verify it with.

    Your port 443 is open from abroad but mine isn't? Are you on the 590 bt plan?

  5. Oops, I'm not familiar with the use of the SSL term, I was thinking HTTPS for port 443 forgetting somebody told me earlier to check it. A newbie error. sorry.

    BTW, 3BB tech support emailed me a couple of questions similar to "is your router plugged in?" last night. After sending them a few screen shots of my router settings and port check results I await their next reponse but it is clear from you guys what it will be. I asked about upgrade options I had.

  6. It is annoying but not the end of the world. I'll buy a Pi for my daughter in Michigan and send an imaged SD to her. I can SSH or Remote Desktop into it from here for further development or maintenance. Switching to True isn't worth trying to explain to the family why. Thanks guys. Now I understand all I need to know. wai2.gif Note to self: send 2 SDs in case overclocking eats one. And also teach her how to backup and restore images. Too bad there isn't a fast way to transmit about 7Gb. Or is there? Maybe Raspbian image files can be compressed. Plus, aren't there ways to FTP with multiple streams? Maybe there is a way to transmit an image in an acceptable time period, like overnight, after all. Comments welcome.

  7. Greetings. For a year now I've been doing Raspberry Pi development, specifically webserver activities. Six months ago I was hosting a few little websites using Lighttpd or Apache2 virtual hosting on my Pi. Then upon returning from the U.S., I recently I tried to install the WordPress Jetpack plugin and found it would not be complete because "site must be public accessible". Port check tools confirmed port 80 is not open. 8080 is but I am to expect public users learn to append :8080 after my domain name? I don't think so.

    I am looking forward to a confirmation that yes, 3BB does this things and secondly, what are my options? I would be willing to pay more for an opened port 80 but not a lot. Thanks

×
×
  • Create New...