Facebook share a link


#1

Facebook does not accept this certificate. Polecy can not approve this. Is this correct? Can not share link on facebook.


#2

Hi @trondnyl,

Can you please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):


#3

Hei ! Takk for svar. Jeg har en server som står i min kjeller. Den er koblet opp til internet via 100Mb fiber linje.
Serveren kjører ubuntu 18.04lts .

Jeg har laget 7 websider virtuelle på denne server og som har en felles Ip adresse.

Alle virket ok og har gjort det i ett par år.

Så bestemte jeg meg for å legge inn SSL sertifikat, og bestemte meg for Lets encrypt.

Dette gikk fint og alle sidene untatt en ble oppdatert til https med sertificat.

Jeg var bortreist fra 15 januar til 17 februar og da var serveren avslått.

Jeg satte serveren på igjen den 18. februar men da var det bare den siden som hadde http altså ikke SSL sertifikat som virket.

Jeg prøvde og finne feilen men klarte det ikke.

I går den 7.april satte jeg tilbake backup fra 1. desember 2018 og slettet log på pc og da var allt ok, men selvsagt uten certifikat. kun http.

Jeg vet ikke hva som har skjedd men jeg får prøve å legge inn igjen ssl på en side først.

mine sider er :

  1. http://eidskog.ddns.net

#4

http://nylokken.ddns.net
https://hb3.ddns.net

https://hb4.ddns.net

https://hb5.ddns.net

https://hyler.ddns.net

https://hb100.ddns.net


#5

Prosessor er P¤ 3Ghz
2 Gb Ram

og bruker wordpress.


#6

Ble en liten feil alle url er nå http:


#7

Hi @trondnyl

checked your first domain, there is no certificate ( https://check-your-website.server-daten.de/?q=eidskog.ddns.net ):

Domainname Http-Status redirect Sec. G
http://eidskog.ddns.net/
87.248.15.221 200 0.473 H
https://eidskog.ddns.net/
87.248.15.221 -2 1.087 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 87.248.15.221:443

Looks like an active blocking firewall.

Same picture with that domain:

Domainname Http-Status redirect Sec. G
http://hyler.ddns.net/
87.248.15.221 200 0.330 H
https://hyler.ddns.net/
87.248.15.221 -2 1.083 V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 87.248.15.221:443

Feel free and check your other domains with my tool. But it looks that all of your https traffic is blocked by a firewall.


#8

Translated your post, using Google:

Hi ! Thanks for reply. I have a server that is in my basement. It is connected to the internet via the 100Mb fiber line.
The server runs ubuntu 18.04lts.

I have created 7 web pages virtual on this server and have a common Ip address.

Everyone seemed ok and have been doing it for a couple of years.

Then I decided to enter the SSL certificate and decided Lets encrypt.

This went fine and all the pages except one were updated to https with certificate.

I was away from January 15 to February 17 and then the server was declined.

I put the server back on February 18, but then it was only the site that had http, not the SSL certificate that worked.

I tried and found the error but couldn’t.

Yesterday, April 7, I set back backup from December 1, 2018 and deleted log on PC and then everything was ok, but of course without certificate. only http.

I don’t know what has happened but I try to re-enter ssl on one page first.

So there are no certificates. And you need a client.

Start there:


#9

If you have an error on Facebook when trying to share a link, it seems likely to me that it has to do with Facebook policies but not with the validity of the certificate.

If there’s an error with a browser, could you please share the error from the browser? And if there’s an error from Facebook, could you please share the error from Facebook?


#10

Yes that is my thaught too. It is the polisy in facebook they do not trust ddns.net


#11

That’s too bad! In that case, I guess you’ll need to get your own domain name in order to create links that can be shared on Facebook.