Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Offers
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

RackNerd's OFFICIAL LET BLACK FRIDAY! HUNDREDS OF GIVEAWAYS + CRAZY DEALS, MASSIVE (come see)

1…808809811813814…953

Comments

  • noob404noob404 Member

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    Exactly, for now, it seems it is more or less where I want it to be. Did a bit more read up and found that it's also better to have the LE certs working alongside CF's Universal SSL, as the former encrypts everything going from origin server to CF, if my understanding is right.

    Anyways, thanks for all the help, dude. Really appreciate it.

    Thanked by 1Beniskickbutt
  • noob404noob404 Member

    @xpress7 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    If the code works, don't touch it. :p

    Especially since I am known to have the anti-Midas touch :lol:

    Thanked by 1Beniskickbutt
  • noob404noob404 Member

    Anybody up? Down for some demand for a GA?

    Thanked by 1Beniskickbutt
  • TrKTrK Member

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    Exactly, for now, it seems it is more or less where I want it to be. Did a bit more read up and found that it's also better to have the LE certs working alongside CF's Universal SSL, as the former encrypts everything going from origin server to CF, if my understanding is right.

    Anyways, thanks for all the help, dude. Really appreciate it.

    Yeah it does it's job good enough. And you are right on that note. LE always on origin unless you don't want origin to be reached outside of CF network.

    Thanked by 1Beniskickbutt
  • noob404noob404 Member

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    Exactly, for now, it seems it is more or less where I want it to be. Did a bit more read up and found that it's also better to have the LE certs working alongside CF's Universal SSL, as the former encrypts everything going from origin server to CF, if my understanding is right.

    Anyways, thanks for all the help, dude. Really appreciate it.

    Yeah it does it's job good enough. And you are right on that note. LE always on origin unless you don't want origin to be reached outside of CF network.

    Thank you. Currently, the proxied domain loads while the proxied subdomain and a non-proxied subdomain throw a DNS_PROBE_FINISHED_NXDOMAIN on Jio Fiber. Hope it's corrected by tomorrow.

    Thanked by 1Beniskickbutt
  • TrKTrK Member

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    Exactly, for now, it seems it is more or less where I want it to be. Did a bit more read up and found that it's also better to have the LE certs working alongside CF's Universal SSL, as the former encrypts everything going from origin server to CF, if my understanding is right.

    Anyways, thanks for all the help, dude. Really appreciate it.

    Yeah it does it's job good enough. And you are right on that note. LE always on origin unless you don't want origin to be reached outside of CF network.

    Thank you. Currently, the proxied domain loads while the proxied subdomain and a non-proxied subdomain throw a DNS_PROBE_FINISHED_NXDOMAIN on Jio Fiber. Hope it's corrected by tomorrow.

    are you using the default DNS servers on jiofiber? if yes it might help update the DNS servers to CF or google DNS, or you should try flushing the DNS cache or try with another device altogether.

    Thanked by 1Beniskickbutt
  • cakeiscakeis Member

    Hello, I would like to double the bandwidth.
    Order: 7238740804
    Thanks!

    Thanked by 1Beniskickbutt
  • noob404noob404 Member

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:

    @TrK said:

    @noob404 said:
    @TrK Finally, it's more stable. Fiddled around with SSL and added CloudFlare Origin certs to the domain. Also, proxied it. It's working fine now. But, now, I have another issue. I have both the Let's Encrypt and the CloudFlare certificates in the server block. Is that risky? Upon checking, I see that browsers only detect the CloudFlare certs.

    You should remove the CF origin cert from the server block if you are going to bypass proxy for a ASN or network. Also CF doesn't serve server block SSL it's only meant as a secure exchange with your server and CF edge. CF will use edge SSL mostly Google trust and LE certs for your website if proxied.

    I did try removing it from the server block. But, browsers just don't recognise the LE certs if I don't have both the CF script in the server block alongside LE and universal SSL enabled on CF.
    My only other option is to disable CF proxy and SSL options on CF and use my LE certs. I'd rather not use CF then. WDYT?

    BTW, sorry for using you as my tech support. I have learned a lot form you. Not that a lot of people are gonna be visiting the website I am building, but, I will definitely be adding you to the credits page.

    Can you share the vhost config and CF SSL settings, there might be something that you missed. I am using the exact same setup with LE on server and strict SSL settings on CF, and if bypass the proxy i am presented directly to the server with server SSL.

    And it's fine, love to help wherever possible, I mean I love doing that.

    Scratch that. You were right. I might have just got it. Okay, so this is what I did:-
    1. Proxied domain and subdomain
    2. Enabled Universal SSL
    3. Disabled Origin certificates (i.e., revoked them and deleted the files from origin server)

    Now, the websites do load on Jiofiber as well with CF's Edge certs (Google Trust). I guess this is what I need.

    Good luck with that, and the old philosophy if it works don't mess it up, Or so the saying goes...

    Exactly, for now, it seems it is more or less where I want it to be. Did a bit more read up and found that it's also better to have the LE certs working alongside CF's Universal SSL, as the former encrypts everything going from origin server to CF, if my understanding is right.

    Anyways, thanks for all the help, dude. Really appreciate it.

    Yeah it does it's job good enough. And you are right on that note. LE always on origin unless you don't want origin to be reached outside of CF network.

    Thank you. Currently, the proxied domain loads while the proxied subdomain and a non-proxied subdomain throw a DNS_PROBE_FINISHED_NXDOMAIN on Jio Fiber. Hope it's corrected by tomorrow.

    are you using the default DNS servers on jiofiber? if yes it might help update the DNS servers to CF or google DNS, or you should try flushing the DNS cache or try with another device altogether.

    Yes, I am using default DNS. Tried flushing DNS cache on my primary device and tried 3 other devices connected to JioFiber.
    As for Google/CF DNS, I believe setting them this issue will be fixed. But, another visitor that might visit wont take the time to set CF DNS just to visit my site

  • OKHaoOKHao Member

    Hi. I would like to double the bandwidth.
    Order Number: 3788802176
    Thanks!

  • noob404noob404 Member

    Good night, RackNerd party! See you in the morning!

  • TrKTrK Member
    edited December 2024

    @noob404 said: Yes, I am using default DNS. Tried flushing DNS cache on my primary device and tried 3 other devices connected to JioFiber.
    As for Google/CF DNS, I believe setting them this issue will be fixed. But, another visitor that might visit wont take the time to set CF DNS just to visit my site

    if a new person visits your site Jio Fiber's router will likely query the DNS from authoritative nameservers, the issue is with their routers storing the DNS cache for quite some time rather than trying to get a new update, I mean almost every router, and DNS server does that. So you are technically fine. The reason i use my own DNS servers is because of this only, i am thinking of modifying my DNS and blocking the Deep packet inspection or DPI. GoodbyeDPI is a good tool but i prefer modifying my DNS server to help me achieve that instead of relying on something else.

  • Ahmad_Ahmad_ Member

    Double chance

    Thanked by 1dustinc
  • DeadlyChemistDeadlyChemist Member

    (base) root@api:~/racknerd-images# ls images/ -1 | wc -l
    1102

    1102 images were generated so far, unsure when this thread closes, but i'll try to send all of the images here at the end

    Thanked by 1dustinc
  • Neat321Neat321 Member

    @DeadlyChemist said:
    (base) root@api:~/racknerd-images# ls images/ -1 | wc -l
    1102

    1102 images were generated so far, unsure when this thread closes, but i'll try to send all of the images here at the end

    You will send them all?

  • Neat321Neat321 Member

    RACKNERD GANG

  • DeadlyChemistDeadlyChemist Member

    @Neat321 said:

    @DeadlyChemist said:
    (base) root@api:~/racknerd-images# ls images/ -1 | wc -l
    1102

    1102 images were generated so far, unsure when this thread closes, but i'll try to send all of the images here at the end

    You will send them all?

    yes
    https://racknerd.thechemicalworkshop.com/gallery

    all of this, all user generated (check my signature..)

    Thanked by 2Neat321 JohnnySac
  • TrKTrK Member

    Can someone confirm if LET is supported with ECH? it's showing not encrypted for me. Although it's experimental it's quite good at what it does.

  • DeadlyChemistDeadlyChemist Member

    shit is fast, had to open a ticket and got an anwser within 20mins... nearly all of racknerd services are excellent

    all i need for christmas is more ram....

    Thanked by 1dustinc
  • icexhicexh Member

    Hello, I would like to double the bandwidth.
    Order: 7485363283
    Thanks!

  • IntzenIntzen Member

    Hello, I would like to double the bandwidth.
    Order: 4989287968
    Thanks!

  • ChrnoChrno Member

    Hello, I would like to double the bandwidth.
    Order: 6908025631
    Thanks!

  • kylesouthkylesouth Member

    Just signed up. Order #2240724186

  • SocheatSocheat Member

    We're up to page 811 now, can we made it to at least 911? :lol:

  • noob404noob404 Member

    Good morning, everyone!

  • cybertechcybertech Member

    MOARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR

  • noob404noob404 Member

    @TrK said:

    @noob404 said: Yes, I am using default DNS. Tried flushing DNS cache on my primary device and tried 3 other devices connected to JioFiber.
    As for Google/CF DNS, I believe setting them this issue will be fixed. But, another visitor that might visit wont take the time to set CF DNS just to visit my site

    if a new person visits your site Jio Fiber's router will likely query the DNS from authoritative nameservers, the issue is with their routers storing the DNS cache for quite some time rather than trying to get a new update, I mean almost every router, and DNS server does that. So you are technically fine. The reason i use my own DNS servers is because of this only, i am thinking of modifying my DNS and blocking the Deep packet inspection or DPI. GoodbyeDPI is a good tool but i prefer modifying my DNS server to help me achieve that instead of relying on something else.

    Yah, totally get it. As for GoodbyeDPI, I have tried this on Windows with JioFiber a few months ago. Didn't do a lot of good.

  • fensuijifensuiji Member

    订货号： 7215007345

    订单编号 2883992416

    Please give me double traffic, thank you

  • noob404noob404 Member

    MAKE SOME DEMAND FOR A RACKNERD GIVEAWAY!

  • xpress7xpress7 Member

    @noob404 said:
    Good morning, everyone!

    Good morning

  • noob404noob404 Member
    edited December 2024

    3 RACKNERD GIVEAWAYS IN DECEMBER - DO NOT MISS OUT !!!

    1. RackNerd Gleam Giveaway - Lottery/Raffle - Ends in ~ 24 days
    2. Main BF 2024 Giveaway - Lottery/Raffle - Winners will be announced on 12/13/2024 @ 8 PM PST
    3. RackNerd BF 2024 Social Butterfly - Engagement-based - Ends on 12/23/2024 @ 11 AM PST

    75-inch TVs, Gaming Laptop, Gaming PC, iPad, RackNerd credits, RackNerd merch and RackNerd Dedi to be won in all of them. Participate in all of them to increase your chances of going home with goodies!

This discussion has been closed.