The weather.gov website has an API where you should be able to get all that information without scraping HTML. Also see https://forecast-v3.weather.gov/documentation. I use this in Weather::WeatherGov (unreleased) to fetch weather data as JSON for a given latitude/longitude

use strict;
use HTTP::Tiny;
use URI;
use JSON 'decode_json';

use Moo 2;
use feature 'signatures';
no warnings 'experimental::signatures';

our $base_uri = URI->new(
        $ENV{PERL_WEATHER_WEATHERGOV_URI}
    #|| 'https://forecast-v3.weather.gov/'
    || 'https://api.weather.gov/points/'
);

my $ua = 
        HTTP::Tiny->new(
            agent => "Weather::WeatherGov/$VERSION",
        );

sub forecast( %options ) {
    my $entry = base_uri . sprintf '%s,%s',
        $options{latitude},
        $options{longitude};
    # We should cache this request for office and grid position
    # maybe store these in the same SQLite database(schema) as Weather
+::MOSMIX?!

    # also, we need a cache and rate-limiter here so we can rate-limit
    # at least by IP address and maybe also globally how much we hit w
+eather.gov
    my $loc = $self->json_request($entry);
    json_request(
        $loc->{properties}->{forecastHourly},
    );
}

sub json_request( $uri ) {
    my $response = $ua->request(GET => $uri, {
        accept => 'JSON-LD',
    } );
    decode_json( $response->{content} );
}
[download]

Not your original question, but have you considered using their API rather than scraping?

(As for the original question, look at the docs for alarm or Sys::SigAction's timeout_call and wrap your hanging call in something like that.)

If the problem is a slow server then just tell LWP::Simple to tell LWP::UserAgent to timeout - (no need to alarm() yourself):

use LWP::Simple qw($ua get); # export the underlying LWP::UserAgent in
+to $ua ...

$ua->timeout(10); # ... and set a timeout on it (seconds)

my $doc = get('...') || die {$pass=0};
[download]

bw, bliako

I offer you this bit of code you can play with (try it with parameter 2 and then with parameter 4):

#!/usr/bin/perl
use strict;
use warnings;

my $delay = shift @ARGV || 1; # parameter
my $timeout = 3; # seconds
eval {
  ## Turn on timer.
  local $SIG{"__DIE__"};
  local $SIG{CHLD};
  local $SIG{ALRM} = sub { die "timed-out\n" };
  alarm $timeout;
  my $verylongprocess = `sleep $delay`;
  alarm 0; # disable alarm
};
die $@ if $@ eq "timed-out\n";
print "No timeout\n";
[download]

it should cover external processes (hence, the 3 local SIG's). Not sure it works on Windows. But give it a try.

edit 2: Yes, it works, but instead of the unix "sleep" use the Windows "timeout" command (available in W7 and W10), like so:

  my $verylongprocess = `timeout $delay`;
[download]

Since I am using a free perl hosting called Zettahost, I am wondering if it is possible maybe they do not let free users fetch web pages, or maybe it's a security issue and they don't want anyone to do that. I don't know. Maybe fetching web pages is a privilege that has not been granted to me. Is that possible? They use a Debian Linux server.

I tried to fetch website data using PHP, and it failed as well. So, there's got to be something with the server or the way it is configured. It's not letting me download anything!

<?php

$fileHTML = file_get_contents('http://www.wzsn.net/');
$title = substr($fileHTML, strpos($fileHTML,'<TITLE>') + 7, strpos($fi
+leHTML,'</TITLE>') - (strpos($fileHTML,'<TITLE>') + 7));
echo $title;

?>
[download]

It says, "Warning: file_get_contents(http://www.wzsn.net/): failed to open stream: Connection refused in /srv/disk13/2468845/www/ildispaintings.com/xget.php on line 7"

Yes it looks like zettahost does not allow outbound network connections by default. I just typed 'Zettahost outbound network connections' in to google and got:

http://zettahost.runhosting.com/faq.html

15. I cannot connect to remote scripts, RSS feeds or use cURL on my website?

The outgoing connections are disabled by default on all accounts for security reasons, however they can be enabled for paid accounts from Hosting Settings section. So all you need to do is go to your panel Hosting Settings section look for "Firewall Options" and click on the "Enable" button.

Free Web hosts generally restrict functions like that to avoid becoming havens for spammers and other Internet ne'er-do-wells. The reason that it is an option for paid accounts is probably because a paid account has a paper trail that (theoretically) gives the host someone to hold accountable for abuse.

Crooks, of course, simply pay with stolen credit cards and move on to the next service when the payments bounce and the account is closed, but usually go straight for the "big" providers that are less likely to be able to keep close eyes on new accounts instead of abusing a paid tier on a free hosting service. At $WORK, I once had to watch the logs extra-closely around @DAYS of the month. That was when our worst abuse bots changed hosting providers like clockwork for several months in a row. Sending complaints was useless, because by the time the other provider acted on a complaint of a password-guessing bot, the account had usually been closed for using stolen payment details, or at least that was what the other abuse departments told us. I guess the miscreants eventually found easier targets or ran out of providers to abuse, but that wave lasted almost a year.