What I would like
visting efkhunt.com or www.efkhunt.com to be forwarded to my heroku blog at https://efkhunt.herokuapp.com/
I currently have the free version, but happy to upgrade to hobby if it helps avoid SSL errors etc.
What I've experienced
Currently : efkhunt.com redirs to http://classical-orangutan-xxxxxxxxxxxxxx.herokudns.com/
www.efkhunt.com gives :
This site can’t provide a secure connection www.efkhunt.com sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
What I've tried
I've tried a number of different tutorials, some of which seem contradictory, or perhaps more likely I've not understood them properly. The GD settings I have currently are :
Type Name Value TTL
A # 184.168.131.xxx 600 seconds
CNAME www thermal-centipede-xxxxx.herokudns.com 1 Hour
CNAME _domainconnect _domainconnect.gd.domaincontrol.com 1 Hour
NS # ns47.domaincontrol.com 1
NS # ns48.domaincontrol.com 1
SOA # Primary nameserver: ns47.domaincontrol.com. 1
I've been doing this over a number of days so I don't think I should have to wait for any further propagation.
Cheers!
For anyone struggling - I think the browser cache was misleading, there was actually an SSL error which was resolved by turning on automated certificate management, which required to upgrade to a hobby dyno.
https://devcenter.heroku.com/articles/automated-certificate-management
Related
Hosting a rails web app on heroku; no recent code changes but about 2 days ago the application started reporting constant H31 misdirect errors. After looking into the documentation, since the application was still accessible I moved on.
The next day users from some of the subdomains could not access the application while others could. The application uses a wildcard certificate and we are behind a WAF. The first thing I tried was checking firewall logs and nothing was showing as blocked. I turned off the firewall and connected the domain directly to the application and still received the H31 stream, after 15 minutes of no change i re-enabled the firewall.
Reached out to the firewall and they said that their logs only showed upstream prematurely closed connection while reading response header
At this point they suggested the issue was most likely on the Heroku DNS servers, so I'm waiting for a response at this point.
Is there anything I can do in the heroku environment that would change this or am I stuck waiting for a response?
Im running a Laravel 6 app on AWC EC-2 instance and have it configured to send mail via Gmail SMTP. Has worked perfect for nearly 2 years. Approx 1-1.5 days ago, the email function started throwing the Connection timed out error.
I tried switching ports, and changing TLS to SSL and no change.
Ive read dozens of threads with the same problem - but no help. Most suggest changing from driver smtp to sendmail - but that breaks all my email-send code.
I tried to telnet smtp.gmail.com 587 from the command line - and get Host is unreachable. There has been NO change to the code, config or setup recently.
My thoughts right now, are either:
AWS have blocked my smtp port,
Google has blocked my IP from sending mail,
My server MAY have reached a limit of some sort (but thought it will un-suspend in 24hrs if the case)
I am not sure HOW or WHERE to find that answer, or if there is another possible problem/solution here. I only have Basic support with AWS - so cant raise a standard tech support q.
Any suggestions would be greatly appreciated.
With thanks - James (Image of error and env below).
My app was rejected today due to 'not supporting IPv6'. I've attached screenshots of the error they received which comes from a Parse.com API call.
I could really use some help on this, as I have no clue where to start with this.
Does anyone know if Parse.com supports IPv6? Or do I need to add something to my code? Do I need to migrate to Parse Server?
Please help =\
---- EDIT ---- 9/22/16
OK so, after my first rejection due to "IPv6" issues, I re-submitted and the app was approved. I'd still like to understand if Parse.com and Parse Server are officially IPv6 compatible but as for now, I'm just happy my app was approved. I'll keep this thread open and will edit it when I find the answer.
I have a parse server hosted on Heroku which doesn't support IPv6 yet (see here). But your server is not the reason why the app is rejected. It is your app which should support IPv6.
A possible solution is to download the latest Parse framework from https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/releases/tag/1.14.2 and replace the old ones. I think it should work.
Below is my comparison with the logs in the console for my app with the two different versions of Parse framework.
I have used Parse.framework and Bolts.framework from Feb 2016 in my Apple TV app and also just got rejected also for not supporting IPv6. I checked the log and found that
nw_resolver_start_crazy_eyeballs_timer Received IPv4 result first, performing crazy eyeballs: waiting 50ms on IPv6 for myapp.herokuapp.com:0.
__nw_resolver_start_crazy_eyeballs_timer_block_invoke Crazy eyeballs timer fired: did not receive IPv6 in time, reporting only IPv4 result for myapp.herokuapp.com:0
nw_resolver_cancel_crazy_eyeballs_timer Cancelling crazy eyeballs timer for myapp.herokuapp.com".
It seems the performance issue comes from the 50ms when the app loads.
I use the latest Parse framework and no "crazy_eyeballs_timer" shows up. The log seems more promising because I can see a IPv6 address in the log now.
nw_resolver_create_dns_service_on_queue Starting host resolution myapp.herokuapp.com:0, flags 0x4000d000
nw_resolver_host_resolve_callback flags=0x3 ifindex=0 error=NoSuchRecord(-65554) hostname=myapp.herokuapp.com. addr=0.0.0.0:0 ttl=60
nw_resolver_host_resolve_callback flags=0x2 ifindex=0 error=NoError(0) hostname=us-east-1-a.route.herokuapp.com. addr=88:ffff::bbbb:afb9.0 ttl=74
Here I changed the addr of my server in the log for security reason.
I will send a new update of my app to review and I believe that it should work. I will leave a comment when it gets accepted :)
I have developed an online store that needs to be added as a subdomain to the blog. I have added the domain on heroku and I did create 2 CNAME records 12 days ago:
sklep.justbeck.com.pl. CNAME justbeck.herokuapp.com.
www.sklep.justbeck.com.pl. CNAME justbeck.herokuapp.com.
The site is available from some networks, but not all. In the begining I though it may be a DNS progapagtion taking slightly longer then usuall, but after 12 days the entries are still not available for most of the whatismydns servers.
I suspect that NS records may be messing with the subdomain:
justbeck.com.pl. NS ns3.netdc.pl.
justbeck.com.pl. NS ns4.netdc.pl.
When I try to remove the NS records I get an error telling me that there must be NS entry.
What NS record should I create so the shop running on a heroku is accesible via a blog subdomain from all networks? Or is the problem somewhere else?
After doing some more investigation I found out that justbeck.com.pl has following servers listed as parent servers:
ns3.netdc.pl. [NO GLUE] [TTL=86400]
ns4.netdc.pl. [NO GLUE] [TTL=86400]
dns107.ovh.net. [NO GLUE] [TTL=86400]
ns107.ovh.net. [NO GLUE] [TTL=86400]
After I did nslookup for sklep.justbeck.com.pl on aformentioned name servers, the netdc respond with:
sklep.justbeck.com.pl canonical name = justbeck.herokuapp.com.
While ovh servers respond with:
** server can't find sklep.justbeck.com.pl: NXDOMAIN
I am convinced now that the cause are the ovh servers. However I cannot remove ovh records since they are not the panel. How do I proceed from here?
All authoritative name servers for the .pl return 4 authoritative name servers for justbeck.com.pl domain:
;QUESTION
justbeck.com.pl. IN NS
;ANSWER
;AUTHORITY
justbeck.com.pl. 86400 IN NS ns3.netdc.pl.
justbeck.com.pl. 86400 IN NS ns4.netdc.pl.
justbeck.com.pl. 86400 IN NS ns107.ovh.net.
justbeck.com.pl. 86400 IN NS dns107.ovh.net.
;ADDITIONAL
The first two look OK but ns107.ovh.net and dns107.ovh.net are missing sklep.justbeck.com.pl and www.sklep.justbeck.com.pl records (though they do resolve for example www.justbeck.com.pl, but even for that name they give a differnet answer than ns3.netdc.pl or ns4.netdc.pl)
If your domain control panel does not list those two domain servers, you should probably contact your domain registrar.
Ive been constantly getting the same error,like
"HTTP 403.9 - Access Forbidden: Too many users are connected Internet Information Services Technical Information".
I went through this site and found this command ->
"C:\Inetpub\AdminScripts\adsutil set w3svc/MaxConnections 40" to set maximum connections.Even after running this command I still have the same error.
Im using IIS V.5.1,Oracle 10g,IE 9.0.
Is there a better way to fix???
Use a bigger number.
If you've got enough money to pay for licencing MS IIS and Oracle then you should be able to afford hardware to support more than 40 concurrent requests (not got your setup / code here to test - I'd expect that the cheapest PC I could buy today would support over 500 concurrent connections running Linux,Apache and MySQL/Postgress).