• 0 Posts
  • 169 Comments
Joined 1 year ago
cake
Cake day: February 15th, 2025

help-circle
  • Depending on where you live, going to IT events and conferences to connect to people in person is even more powerful. Ask them about their work and talk passionately about related stuff that you have some knowledge/skill in. Exchange contacts, say you’re looking for work.

    For example, next month is DEVWORLD in amsterdam. They always give away free tickets close to the start of the event. I’m sure there are a ton more like this around the world.


    As for writing applications: For me writing very high quality applications did the trick.

    • only apply to companies/positions that you are REALLY interested in
    • research the position
    • research the company
    • if you can find somebody that works there in a similar position, ask them some questions
    • use the info you gathered to show interest in your appplication
    • write everything yourself, no AI writing. Be a genuine human.
    • But you can use AI to give it the position and your application and tell it to make a hiring decision with pro/con arguments and rework it based on that
    • make a small demo project that shows off your relevant skills and tell them about the challanges you had and what you learned to overcome them

    (About the last point: I found that talking about relevant hobby projects I did and showing the code made a huge difference)

    It usually takes me about a week to write one such application. But I only sent out 3 before hearing back from 2 of the companies and getting signed on by one.

    I know it’s a lot more hoops then just clicking “auto apply” or “apply with AI”, but the effort pays off.

    Contrary to that I often see people complaining online about how they wrote 100 applications in a month and got no job interviews… yeah buddy. (And I was initially one of those people)





  • Sounds good.

    Hmm next you probably should confirm ports 80 and 443 are actually reachable from the internet.

    Use an online port checker like https://canyouseeme.org/

    After that you should check your apache config like somebody else already suggested. I haven’t used apache in a while but if I remember correctly:

    Ensure it says: Listen 80 NOT: Listen 127.0.0.1:80

    (and same with 443)

    Also check your VirtualHost — it should look something like:

    <VirtualHost *:80>
        ServerName yourdomain.com
        DocumentRoot /var/www/wordpress
        # ... other settings
    </VirtualHost>
    

    (and same with 443)


  • Njalla’s default TTL for DNS records is 3600 seconds (1 hour). If you just created or modified the A record, it can take up to that full hour for the change to propagate across the internet, which would perfectly explain why Certbot is connecting to the right IP but failing to fetch the file (the request might be hitting an old IP or a cached null response).

    Before changing any more configurations, you should verify what the rest of the internet is actually seeing for your domain right now.

    Check the current DNS record

    You can usedig to see exactly what IP your domain is resolving to, and importantly, the remaining TTL on that record.

    From your local machine (or any computer), run:

    dig yourdomain.com +noall +answer
    

    This will output something like:

    yourdomain.com.    3412    IN      A       203.0.113.45
    

    The second column (3412) is the remaining TTL in seconds. If that number is counting down from 3600, the record is still propagating. If the IP address shown there doesn’t match your server’s current public IP, the change hasn’t taken effect yet for that DNS server.

    Check from a different perspective

    To ensure it’s not just your local ISP or router cache serving an old record, query an external public DNS server directly:

    dig yourdomain.com @1.1.1.1 +noall +answer
    dig yourdomain.com @8.8.8.8 +noall +answer
    

    If these external servers show the correct IP but Certbot still fails, the DNS is fine, and the problem is somewhere in your network routing or web server config. If they show a wrong IP or no record at all, you simply need to wait for the TTL to expire.















  • afaik you just listed features that the printer I mentioned (or if I am wrong, other similar printers) supports

    it’s my bad for not mentioning all possible workflows, I was just a bit lazy and thinking of my personal documents only, which do not work well with further smart automation, because my batches are highly irregular. So the more manual approach is the best for me currently. Maybe possible with some future AI integration.