The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
So the first message I got when CP was down a short while ago:
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
And I was so inspired knowing that they were working on how to handle the happenstance wherein there was an error in the above custom error page, as well.
it seems swears aren’t noticed in the middle of words
Yeah, this is a tricky one because we still need to allow everyone to talk about shitake mushrooms and cockateels. Not sure I want to add every variation of every naughty word into our filter. I'm sure I'd get plenty of volunteers offering their help should I want it.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved.
That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore...
1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI).
2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed.
3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed.
4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days).
5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!!
Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too.
It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work).
But that number 5 is really ruining my day.
I'm getting some 403 Forbidden status and I really don't know why.
I can't really find any differences with my ASP.NET Core web services...
My Google-fu is leaving me hanging as well.
Ah well, let's stay positive, 4 out of 5 isn't bad
Perhaps I'll wake up in the middle of the night and I'll have my answer.
At least the websites work with a custom domain name and a valid certificate.
The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway
This reminds me of the argument between a husband and wife. She was talking about mixed feelings, but her husband insisted that the concept was nonsense, because everything was ultimately positive or negative.
"Out of all your friends", she replied, "you have the biggest dick."