SA-MP Forums Archive
SAMP offline - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP (https://sampforum.blast.hk/forumdisplay.php?fid=3)
+--- Forum: Client Support (https://sampforum.blast.hk/forumdisplay.php?fid=16)
+--- Thread: SAMP offline (/showthread.php?tid=627299)



SAMP offline - Savana221 - 26.01.2017

I'm interested in why samp wiki offline, as I learned on this wiki, and now he's gone ..

And why is all about samp offline ??

Do Samp failed?


Re: SAMP offline - princejeet1510 - 26.01.2017

Nope it's working....
Do
HTTPS to HTTP...
It's working but they didn't updated something....I think.


Re: SAMP offline - Sew_Sumi - 26.01.2017

No, it was down, and now it's working...


Re: SAMP offline - Savana221 - 26.01.2017

Sites can not be retrieved

Owner www.sa-mp.com refused to connect.
Try the following:
check the connection
check the proxy and firewall


Re: SAMP offline - FFAKO - 26.01.2017

its still down i cant connect to samp wiki too :/


Re: SAMP offline - Sew_Sumi - 26.01.2017

Up for me, it could be having sporadic issues though. When I said it was up, it had been "down" for 2 days for me.

But that could just have been for the times I was trying it.

One way of making things "work" is to go ****** the function you're looking at in ******, and check the cached version.


Re: SAMP offline - Wolfe - 26.01.2017

replace https with http you'll be able to use it.

~ Didn't read other replies, my fault.


Re: SAMP offline - Sew_Sumi - 26.01.2017

Quote:
Originally Posted by Wolfe
Посмотреть сообщение
replace https with http you'll be able to use it.

~ Didn't read other replies, my fault.
That is probably why it's sporadic for me as I've been googling the function, and that returns an HTTPS link, and when I go to the site, it comes back for HTTP...


Re: SAMP offline - mickmelon - 26.01.2017

It's like we have all been abandoned. No one is fixing this https issue and the forum is full of spam! Pain in the ass if you ask me.


Re: SAMP offline - Sew_Sumi - 26.01.2017

It's not an issue if you can work around it...