$500 to anyone who...

[Andrew Stolarz]

Das,

The problem is that i'm not able to reach http://goravani.com/ ..... it
redirects to the secure page https://goravani.com/

You need to turn off any site redirects (temporarily until it's all
validated etc) so that it can communicate on the port 80.


Andrew




On Sun, Mar 6, 2022 at 8:23 PM Das Goravani <goravanis at gmail.com> wrote:

> Dear Bas,
>
> That’s so strange that you looked into my cert and saw only Goravani.com
> covered. I made it to be a multi domain cert, 3 domains, or 4, covering
> their www versions as well. That’s so strange.
>
> Indeed, I switched just now to another multi domain cert that is working
> well for one of the domains and bingo, this site started working well also.
> So my first cert really was at fault. That is so odd. It comes from
> Certbot, You’d think nothing could be wrong.
>
> Do you have any idea why Certbot would say that a site isn’t listening on
> port 80 as a virtual host when in fact you can pull up the site in an
> insecure way now proving it is listening.
>
> Further Certbot says that that sites document root folder is not a
> directory when in fact it is working to serve the site in an insecure way.
>
> Folder not a folder, site not listening that you can pull up?
>
> Why does Certbot get these two important things wrong? They are preventing
> me from getting a certificate for the site.
>
> Does anything at all pop into your mind that I could check.. like "no
> virtual host listening on port 80" when I try to run that site? It is setup
> identical to the others which are working fine now. 3 other working fine,
> this one has one of these two problems when I try to get a cert two
> different ways through Certbot. (Letsencrypt)
>
> Any help appreciated.
>
> Das
>
>
>
> > On Mar 6, 2022, at 7:30 PM, Bastiaan Olij <bastiaan at muxworks.com.au>
> wrote:
> >
> > Hi Das,
> >
> > Examining your certificate, it's common name is goravani.com, and then
> under Subject Alt Names only goravani.com is listed. This would mean the
> certificate only works for this specific address and not for any of its
> derivatives so indeed https://goravani.com is fine,
> https://www.goravani.com isn't covered by this certificate.
> >
> > You mentioned in one of your other posts that you're using a multi
> domain certificate but in that case there should be several entries under
> the Subject Alt Names section. If you are using a single site certificate
> you probably want it to be "*.goravani.com" so that it also covers the
> www version. You may want to talk to someone at the organization that
> provides you with your certificate for help here.
> >
> > Also while I'm looking at your site, to make it fully secure you also
> need to make sure no parts of your website contains URLs with http in it.
> For instance href='http://fonts.googleapis.com/css?family=Anton' should
> become href='https://fonts.googleapis.com/css?family=Anton'. I'm not sure
> if this is important in the json at the top of your page, I don't think so.
> >
> > Cheers,
> >
> > Bas
> >
> > On 7/03/2022 4:46 am, Das Goravani wrote:
> >> $500 to anyone who can solve my hosting issues.
> >>
> >> I have exhausted my own abilities to fix my issues.
> >>
> >> Today I have received an email from Google stating that my main site,
> Goravani.com, will not be indexed because of server issues.
> >>
> >> That is VERY bad. I can’t have that lingering. I MUST solve these
> issues.
> >>
> >> Try https://www.goravani.com <https://www.goravani.com/>
> >>
> >> You will most likely get a block, a warning, saying that the connection
> is not private, not secure.
> >>
> >> That is causing my issue with Google. That hang up.
> >>
> >> My site works fine with https and no WWW.. but with WWW it messes up.
> >>
> >> That is the major issue.
> >>
> >> Once we solve that we can move on to copy settings we come up with to
> my other few sites that are setup the same way.
> >>
> >> Then there’s an issue with one site whereby I cannot get a certificate
> for it. Certbot says that the site is not a listening virtual host on port
> 80. This is most odd because the site works. And it is setup identically to
> my other sites which DO get certificates just fine. When I try to get a
> cert for this one site the normal way it says it’s not listening on port
> 80. When I try to get a cert another way, using the keyword "certainly"
> then it says the document root folder is not a directory. But the site is
> working, including it’s document root directory. So that is most odd.
> >>
> >> So if you’re willing to get your hands dirty, do a video screen session
> with TeamViewer or some viewer, into my server, and go over my accounts
> with NO-IP and on my server, get into the certificates and figure out these
> problems, then $500 is yours if we can at least "Validate Fix" with Google,
> on the first problem. When I am done fixing then I click the Validate Fix
> button on Google’s site to see if they agree the problem is fixed. If it’s
> fixed then my site will index. That’s the goal.
> >>
> >> You can start by clicking these links to see if you get any warnings or
> super slow behavior on any of them:
> >>
> >> https://goravani.com
> >> https://jyotishstudio.com <https://jyotishstudio.com/>
> >> https://readmyastrology.com <https://readmyastrology.com/>
> >> https://goravanijyotish.com <https://goravanijyotish.com/>
> >>
> >> https://www.goravani.com
> >> https://www.jyotishstudio.com <https://www.jyotishstudio.com/>
> >> https://www.readmyastrology.com <https://www.readmyastrology.com/>
> >> https://www.goravanijyotish.com <https://www.goravanijyotish.com/>
> >>
> >> http://www.goravani.com
> >> http://www.jyotishstudio.com <http://www.jyotishstudio.com/>
> >> http://www.readmyastrology.com <http://www.readmyastrology.com/>
> >> http://www.goravanijyotish.com <http://www.goravanijyotish.com/>
> >>
> >> Problems on any of these links is not acceptable. Finishing the $500
> requirement is to have all these links working swiftly or correctly and my
> certificate issues resolved.
> >>
> >> Personally I think I have everything setup correctly already. It is I
> think something beneath the level of what is typed into my various accounts
> on various setup windows. It’s deeper than that.
> >>
> >> It is odd because my sites are setup identically. But they are behaving
> differently.
> >>
> >> Please consider helping me if you are familiar with this area of
> endeavor.
> >>
> >> Thank you,
> >>
> >> Das Goravani
> >>
> >> Ps: I’m in Florida, so it’s the Eastern US Time Zone of -5. I am using
> a Mac Server on Catalina. Apache. NO-IP for DNS, MAMP for managing Apache.
> >>
> >> All my problems started when I tried to get a new certificate recently.
> Up til then everything worked, including Google indexing. You could type
> http or https and you could type WWW or no .. all variations worked, and
> Google worked. So it is possible to get this working. I have changed
> nothing, just something got broke when I tried to get a new cert recently.
> For what that is worth…
> >>
> >>
> >>
> >> _____________________________________________________________
> >> Manage your list subscriptions at https://lists.omnis-dev.com
> >> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
> >
> > --
> > Kindest Regards,
> >
> > Bastiaan Olij
> > bastiaan at muxworks.com.au
> > +61-432144833
> >
> > _____________________________________________________________
> > Manage your list subscriptions at https://lists.omnis-dev.com
> > Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>