Windows Internet Information Services (IIS) is Microsoft’s robust, enterprise-grade web server designed to host web applications and services. It’s tightly integrated with the Windows Server platform and widely used for everything from static sites to dynamic web apps built with ASP.NET, PHP, or Python.

In this guide, we’ll walk through what IIS is, its key components, common use cases, how to configure it, and ways to troubleshoot typical issues.

What Is Windows Internet Information Services (IIS)?#

IIS is a feature-rich web server that supports multiple protocols including HTTP, HTTPS, FTP, FTPS, SMTP, and WebSocket. It’s often chosen in Windows-centric environments for its performance, flexibility, and ease of use.For an official overview, check out Microsoft’s IIS documentation.

It can host:

• Static websites
• Dynamic applications using ASP.NET, PHP, or Python
• Web services and APIs

IIS provides powerful security controls, application isolation via application pools, and extensive monitoring features.

Key Components of Windows IIS Web Server#

IIS Manager#

The graphical user interface for managing IIS settings, websites, and application pools.

Web Server#

Handles incoming HTTP(S) traffic and serves static or dynamic content.

Application Pools#

Isolate applications to improve stability and security. Each pool runs in its own worker process.

FastCGI#

Used to run non-native apps like PHP or Python. For Python apps, IIS commonly uses wfastcgi to bridge communication. Learn more about hosting Python apps on IIS.

SSL/TLS Support#

IIS makes it easy to configure HTTPS, manage SSL certificates, and enforce secure connections.

Top Features and Benefits of IIS#

Security & Authentication#

Supports multiple authentication schemes like Basic, Integrated Windows Auth, and custom modules. Can be tied into Active Directory.

Logging & Diagnostics#

Robust logging and diagnostics tools to help troubleshoot performance and runtime issues.For troubleshooting guides, visit Microsoft’s IIS troubleshooting resources.

Performance & Scalability#

Features like output caching, dynamic compression, and bandwidth throttling help scale under load.

Step-by-Step Guide to Installing and Configuring IIS on Windows Server#

Install IIS#

1. Open Server Manager → Add Roles and Features
2. Choose Web Server (IIS) and complete the wizard
3. Launch IIS Manager using inetmgr in the Run dialog

Add a Website#

1. In IIS Manager, right-click Sites → Add Website
2. Set Site name, physical path, and port
3. Optionally bind a domain or IP

Configure Application Pool#

Each new website creates a pool, but you can customize it:

• Set .NET version
• Change identity settings
• Enable recycling

Enable HTTPS#

1. Right-click site → Edit Bindings
2. Add HTTPS binding with an SSL certificate

Set File Permissions#

Ensure that IIS has read (and optionally write) permissions on your site directory.

Troubleshooting Common IIS Issues and Solutions#

Website Not Starting#

• Check event logs for errors
• Ensure app pool is running
• Confirm no port conflicts

Permission Denied Errors#

• Confirm folder/file permissions for IIS user

Python FastCGI Issues#

• Validate wfastcgi.py installation
• Confirm FastCGI settings in IIS Manager

Slow Performance#

• Enable caching and compression
• Use performance monitor tools

For more community-driven insights, explore the Microsoft IIS Tech Community.

Conclusion: Maximizing IIS for Your Windows Web Hosting Needs#

IIS remains a top-tier web server solution for Windows environments. Whether you're running enterprise ASP.NET applications or lightweight Python services, IIS delivers in performance, security, and manageability.

With the right setup and understanding of its components, you can confidently deploy and manage scalable, secure web infrastructure on Windows Server.

Looking to streamline your cloud infrastructure, application delivery, or DevOps workflows? Visit nife.io/solutions to discover powerful tools and services tailored for modern application lifecycles. and specialized support for Unreal Engine app deployment in cloud environments.

When managing Kubernetes workloads on AWS EKS, using a LoadBalancer for each service can quickly become expensive and inefficient. A cleaner, scalable, and more cost-effective solution is to use an Ingress Controller like NGINX to expose multiple services via a single LoadBalancer. This blog will walk you through how I set up Ingress in my EKS cluster using Helm, configured host-based routing, and mapped domains through Cloudflare.

Prerequisites#

• AWS EKS Cluster set up
• kubectl, helm, and aws-cli configured
• Services already running in EKS
• Cloudflare account to manage DNS

Get started with EKS in the AWS EKS User Guide.

Step 1: Install NGINX Ingress Controller on EKS using Helm#

This will install the NGINX Ingress Controller and expose it through a LoadBalancer service. You can get the external ELB DNS using:

Note the EXTERNAL-IP of the nginx-ingress-controller—this is your public ELB DNS.

Learn more about NGINX Ingress at the official Kubernetes documentation.

Step 2: Create Your Ingress YAML for Host-Based Routing#

Below is an example Ingress manifest to expose a service using a custom domain:

Apply the file using:

Step 3: Configure DNS for NGINX Ingress with Cloudflare#

Go to your Cloudflare dashboard and create a CNAME record:

• Name: metube-app-622604 (or any subdomain you want)
• Target: your NGINX LoadBalancer DNS (e.g., a1b2c3d4e5f6g7.elb.amazonaws.com)
• Proxy status: Proxied ✅

Wait for DNS propagation (~1–5 minutes), and then your service will be available via the custom domain you configured.

Understand DNS management in Cloudflare with the Cloudflare DNS docs.

Verify NGINX Ingress Routing and Domain Configuration#

Try accessing the domain in your browser:

You should see the application running from port 8081 of the backend service.

Reference Document#

For more detailed steps and examples, check out this shared doc:
🔗 Ingress and DNS Setup Guide

Benefits of Using NGINX Ingress with Single LoadBalancer#

• Cost-effective: One LoadBalancer for all services.
• Scalable: Add new routes/domains by just updating the Ingress.
• Secure: Easily integrate SSL with Cert-Manager or Cloudflare.
• Customizable: Full control over routing, headers, and rewrites.

Conclusion: Efficient Multi-Service Exposure in EKS with NGINX#

Exposing multiple services in EKS using a single LoadBalancer with NGINX Ingress can streamline your infrastructure and reduce costs. Just remember:

• Use Helm to install and manage the NGINX Ingress Controller
• Configure host-based routing to serve multiple domains through one point
• Use Cloudflare DNS to map custom domains to your LoadBalancer
• Regularly test and validate access for each new service

With just a few commands and configurations, you can build a scalable and efficient ingress setup—ready for production.

Learn how to add and manage EKS clusters with Nife’s AWS EKS integration guide.

Learn how to add standalone Kubernetes clusters with Nife’s standalone cluster setup guide.

When managing Kubernetes workloads on AWS EKS, using a LoadBalancer for each service can quickly become expensive and inefficient. A cleaner, scalable, and more cost-effective solution is to use an Ingress Controller like NGINX to expose multiple services via a single LoadBalancer. This blog will walk you through how I set up Ingress in my EKS cluster using Helm, configured host-based routing, and mapped domains through Cloudflare.

Prerequisites#

• AWS EKS Cluster set up
• kubectl, helm, and aws-cli configured
• Services already running in EKS
• Cloudflare account to manage DNS

Get started with EKS in the AWS EKS User Guide.

Step 1: Install NGINX Ingress Controller on EKS using Helm#

This will install the NGINX Ingress Controller and expose it through a LoadBalancer service. You can get the external ELB DNS using:

Note the EXTERNAL-IP of the nginx-ingress-controller—this is your public ELB DNS.

Learn more about NGINX Ingress at the official Kubernetes documentation.

Step 2: Create Your Ingress YAML for Host-Based Routing#

Below is an example Ingress manifest to expose a service using a custom domain:

Apply the file using:

Step 3: Configure DNS for NGINX Ingress with Cloudflare#

Go to your Cloudflare dashboard and create a CNAME record:

• Name: metube-app-622604 (or any subdomain you want)
• Target: your NGINX LoadBalancer DNS (e.g., a1b2c3d4e5f6g7.elb.amazonaws.com)
• Proxy status: Proxied ✅

Wait for DNS propagation (~1–5 minutes), and then your service will be available via the custom domain you configured.

Understand DNS management in Cloudflare with the Cloudflare DNS docs.

Verify NGINX Ingress Routing and Domain Configuration#

Try accessing the domain in your browser:

You should see the application running from port 8081 of the backend service.

Reference Document#

For more detailed steps and examples, check out this shared doc:
🔗 Ingress and DNS Setup Guide

Benefits of Using NGINX Ingress with Single LoadBalancer#

• Cost-effective: One LoadBalancer for all services.
• Scalable: Add new routes/domains by just updating the Ingress.
• Secure: Easily integrate SSL with Cert-Manager or Cloudflare.
• Customizable: Full control over routing, headers, and rewrites.

Conclusion: Efficient Multi-Service Exposure in EKS with NGINX#

Exposing multiple services in EKS using a single LoadBalancer with NGINX Ingress can streamline your infrastructure and reduce costs. Just remember:

• Use Helm to install and manage the NGINX Ingress Controller
• Configure host-based routing to serve multiple domains through one point
• Use Cloudflare DNS to map custom domains to your LoadBalancer
• Regularly test and validate access for each new service

With just a few commands and configurations, you can build a scalable and efficient ingress setup—ready for production.

Learn how to add and manage EKS clusters with Nife’s AWS EKS integration guide.

Learn how to add standalone Kubernetes clusters with Nife’s standalone cluster setup guide.

Amazon S3 (Simple Storage Service) is one of the most popular cloud storage solutions. Whether you're hosting static websites, sharing media files, or distributing software packages, there are times when making your S3 bucket public is necessary. But how do you do it without compromising security? Let’s walk through it step-by-step.

Why Make an S3 Bucket Public? Common Use Cases?#

S3 allows you to store and retrieve any amount of data, from anywhere, at any time. Public access is useful when you want your files to be openly downloadable—no credentials needed. Use cases include:

• Hosting a static website
• Sharing public documentation
• Providing downloadable files like media, zip archives, or datasets

Important: Be cautious—public access means anyone on the internet can view or download those files.

How to Make Your S3 Bucket Public#

There are two primary ways to make files in your S3 bucket publicly accessible:

1. Use a Bucket Policy for Full Public Access#

This method grants public access to all objects within a bucket.

Example Policy:#

• What it does: Allows anyone to perform s3:GetObject (i.e., download files).
• How to apply it:

• When to use: Great for hosting full public websites or making all files downloadable.

  For a deeper dive into IAM policies, visit AWS IAM Policies.

2. Use ACLs for Single File Access#

You can make just one file public without exposing the whole bucket.

Example:#

• What it does: Grants public read access to just myfile.zip.

• When to use: When you only want to share select files and keep others private.

  For more details on managing ACLs, see AWS ACL Documentation.

What Can You Do with Public S3 Access?#

Making files public isn’t just convenient—it can power your apps and workflows:

• Static Websites: Serve HTML/CSS/JS directly from S3.

• Public Downloads: Let users grab resources without signing in.

• Media Hosting: Share images, videos, or documents in a lightweight, scalable way.

  Looking for an easy way to manage your static websites? Check out Amazon S3 Static Website Hosting.

Security Tips Before You Go Public#

Before making your S3 bucket public, keep these tips in mind:

• Security: Double-check that no sensitive data is exposed.

• Use the right method: Policies for full-bucket access, ACLs for individual files.

• Monitor usage: Enable access logs and CloudTrail to audit activity.

  Learn more about monitoring with AWS CloudTrail Logs.

Final Thoughts: Public Access with Precision#

Making your S3 bucket (or objects) public can unlock powerful use cases—from hosting content to sharing files freely. Just remember:

• Use bucket policies for broad access
• Use ACLs for targeted, file-specific access
• Monitor and audit access to stay secure

With just a few AWS CLI commands, your content can go live in minutes—safely and intentionally.

Looking to scale your infrastructure seamlessly? Supercharge your containerized workloads by adding AWS EKS clusters with Nife.io!

Tired of complex, time-consuming deployments? Nife.io makes it effortless with One-Click Deployment—so you can launch applications instantly, without the hassle.

When you're working with text files—be it config files, logs, or source code—you may need to delete specific lines based on their line numbers. This might sound intimidating, but it’s actually quite easy once you know which tool to use.

In this post, we’ll walk through several methods to remove lines using line numbers, using command-line tools like sed, awk, and even Python. Whether you're a beginner or a seasoned developer, there’s a solution here for you.

The Basic Idea#

To delete a specific range of lines from a file:

1. Identify the start line and end line.
2. Use a tool or script to remove the lines between those numbers.
3. Save the changes back to the original file.

Let’s break this down by method.

1. Using sed (Stream Editor)#

sed is a command-line utility that’s perfect for modifying files line-by-line.

Basic Syntax#

• Replace START_LINE and END_LINE with actual numbers.
• d tells sed to delete those lines.

Example#

To delete lines 10 through 20:

With Variables#

📚 More on sed line deletion

2. Using awk#

awk is a pattern scanning tool. It’s ideal for skipping specific lines.

Syntax#

Example#

This prints all lines except lines 10 through 20.

📚 Learn more about awk

3. Using head and tail#

Perfect when you only need to chop lines off the start or end.

Example#

Delete lines 10 to 20:

• head -n 9 gets lines before line 10.
• tail -n +21 grabs everything from line 21 onward.

📚 tail command explained

4. Using perl#

perl is great for more advanced file manipulation.

Syntax#

Example#

• $. is the line number variable in perl.

📚 Perl I/O Line Numbering

5. Using Python#

For full control or if you’re already using Python in your workflow:

Example#

Python is especially useful if you need to add logic or conditions around what gets deleted.

📚 Working with files in Python

Conclusion#

There are plenty of ways to delete lines from a file based on line numbers:

• Use sed for simple, fast command-line editing.
• Choose awk for conditional line selection.
• Go with head/tail for edge-case trimming.
• Try perl if you’re comfortable with regex and quick one-liners.
• Opt for Python when you need logic-heavy, readable scripts.

Explore Nife.io for modern cloud infrastructure solutions, or check out OIKOS to see how edge orchestration is done right.

If you’ve ever tried setting up a web application, you know how messy it can get—installing servers, configuring databases, dealing with software versions. That’s where Bitnami steps in to make your life easier.

In this post, we’ll break down what Bitnami is, why it’s so well-loved, and how you can start using it—whether you’re testing apps locally or deploying to the cloud.

What is Bitnami? All-in-One App Stack for Local & Cloud Deployments#

Think of Bitnami as your all-in-one app launcher. It provides pre-configured software stacks—basically bundles of apps like WordPress, Joomla, or Moodle, with all their required dependencies baked in.

You can run Bitnami on:

• Your local computer (Mac, Windows, Linux).
• Cloud providers like AWS, Google Cloud, or Azure.
• Containers using Docker or Kubernetes.

Each Bitnami stack includes the app, a web server (like Apache), a database (like MySQL), and scripting languages (PHP, Python, etc.). It’s ready to go out of the box.

Explore Bitnami Application Catalog

Why Developers and Teams Love Bitnami#

People love Bitnami because it makes app deployment almost effortless:

• Zero hassle setup: No need to configure every component manually.
• Works anywhere: Use it locally or on your favorite cloud.
• Security focused: Regular updates and patches.
• Totally free: Perfect for students, developers, and small teams.

Bitnami is especially handy when you're short on time but need something reliable and scalable.

How to Start Using Bitnami for App Deployment#

Step 1: Pick an App#

Go to the Bitnami website and choose the app you want—like WordPress, Redmine, or ERPNext.

Step 2: Choose How You Want to Run It#

• Local install: Download the stack for your OS.
• Cloud deployment: Launch the app directly to AWS, Azure, or GCP with one click.
• Containers: Use their Docker images for ultimate portability.

Step 3: Follow the Setup Wizard#

Bitnami installers are beginner-friendly. Just follow the wizard, and your app will be up and running in minutes.

Here’s a step-by-step tutorial on deploying Bitnami WordPress on AWS

Bitnami Use Cases: From Dev Testing to Full Cloud Hosting#

Here are a few awesome use cases:

Test and Build Websites#

Create a local WordPress site to try out new themes and plugins without risking your live website.

Set Up E-Learning Platforms#

Deploy Moodle or Open edX for hosting online courses easily.

Developer Sandboxes#

Developers use Bitnami stacks to test APIs, apps, or backend systems quickly.

Run Business Tools#

Launch tools like Redmine for project tracking or ERPNext for business management.

Learn Cloud Hosting#

Bitnami removes the friction from deploying apps to the cloud, making it easier for beginners to experiment.

Read more about app deployment strategies

When and Why Bitnami is the Right Choice#

Here’s when Bitnami is the right fit:

• You want your app running in minutes, not hours.
• You don’t want to stress over configuration and dependencies.
• You like security and want regular patches without manual updates.
• You want to try different environments with minimal setup.

It’s also a great stepping stone into cloud development and containerization.

Final Thoughts: Bitnami = Instant App Deployment#

Bitnami is like the friendly co-pilot every dev wishes they had—it gives you a head start by simplifying app deployment and making experimentation frictionless.

Whether you're building a blog, launching a learning platform, or playing around with cloud architecture, Bitnami’s got your back.

Check out how nife.io manages fast deployments to see how we build scalable services at the edge.

Nife supports seamless Marketplace Deployments, enabling faster and more consistent app rollouts across environments.

When you're building a web or mobile app, one of the first things you’ll need is a way to let users log in securely. That’s where Amazon Cognito comes in. It helps you manage authentication without having to build everything from scratch.

In this post, we’ll break down how to use Amazon Cognito with the OAuth 2.0 Authorization Code Grant flow—the secure and scalable way to handle user login.

What is Amazon Cognito? How It Helps with Login#

Amazon Cognito is a user authentication and authorization service from AWS. Think of it as a toolbox for managing sign-ups, logins, and secure access to your app. Here’s what it can do:

• Support multiple login options: Email, phone, or social logins (Google, Facebook, Apple).
• Manage users: Sign-up, sign-in, and password recovery via user pools.
• Access AWS services securely: Through identity pools.
• Use modern authentication: Supports OAuth 2.0, OpenID Connect, and SAML.

📚 Learn more in the Amazon Cognito Documentation

Benefits of Using Amazon Cognito#

• Scales with your app: Handles millions of users effortlessly.
• Secure token management: Keeps user credentials and sessions safe.
• Easy social logins: No need to build separate Google/Facebook integration.
• Customizable: Configure user pools, password policies, and even enable MFA.
• Tightly integrated with AWS: Works great with API Gateway, Lambda, and S3.

It’s like plugging in a powerful login system without reinventing the wheel.

🔍 Need a refresher on OAuth 2.0 concepts? Check out OAuth 2.0 and OpenID Connect Overview

How Amazon Cognito Works (User Pools vs. Identity Pools)#

Cognito is split into two parts:

1. User Pools#

• Handles user sign-ups, sign-ins, and account recovery.
• Provides access_token, id_token, and refresh_token for each user session.

2. Identity Pools#

• Assigns temporary AWS credentials to authenticated users.
• Uses IAM roles to control what each user can access.

When using OAuth 2.0, most of the action happens in the user pool.

Step-by-Step: How to Use OAuth 2.0 Authorization Code Grant Flow#

Step 1: Create a User Pool#

1. Head over to the AWS Console and create a new User Pool.
2. Under App Clients, create a client and:
   • Enable Authorization Code Grant.
   • Set your redirect URI (e.g., https://yourapp.com/callback).
   • Choose OAuth scopes like openid, email, and profile.
3. Note down the App Client ID and Cognito domain name.

💡 Want to see this in action with JavaScript? Here's a quick read: Using OAuth 2.0 and Amazon Cognito with JavaScript

Step 2: Redirect Users to Cognito#

When someone clicks "Log In" on your app, redirect them to Cognito's OAuth2 authorize endpoint:

After login, Cognito will redirect back to your app with a code in the URL:

📘 For more on how this flow works, check OAuth 2.0 Authorization Code Flow Explained

Step 3: Exchange Code for Tokens#

Use the code to request tokens from Cognito:

Step 4: Use the Tokens#

Once you get the tokens:

• access_token: Use this to call your APIs.
• id_token: Contains user info like name and email.
• refresh_token: Helps you get new tokens when the current one expires.

Example API call:

When Should You Use Authorization Code Grant Flow?#

This flow is ideal for server-side apps. It keeps sensitive data (like tokens) away from the browser, making it more secure.

Benefits of Using Cognito + OAuth 2.0 Together#

• Security-first: Tokens are exchanged on the backend.
• Scalable: Works even if your app grows to millions of users.
• AWS-native: Plays nicely with other AWS services.

Final Thoughts: A Simple, Secure Login with Cognito + OAuth 2.0#

Amazon Cognito takes the pain out of managing authentication. Combine it with OAuth 2.0’s Authorization Code Grant, and you’ve got a secure, scalable login system that just works. Start experimenting with Cognito and see how quickly you can secure your app. Stay tuned for more tutorials, and drop your questions below if you want help with setup!

If you're looking to take your environment management further, check out how Nife handles secrets and secure configurations. It's designed to simplify secret management while keeping your workflows safe and efficient.

Nife supports a wide range of infrastructure platforms, including AWS EKS. See how teams are integrating their EKS clusters with Nife to streamline operations and unlock more value from their cloud environments.

So, you're setting up PHP and things aren't going as smoothly as you hoped. Maybe you're staring at a php -v error or wondering why your server is throwing a 502 Bad Gateway at you. Don’t sweat it—we’ve all been there.

In this guide, we’re going to walk through the most common PHP installation issues, explain what’s happening behind the scenes, and show you how to fix them without losing your sanity. Whether you’re setting up PHP for the first time or maintaining an existing server, there’s something here for you.

Install PHP on Ubuntu Server

Components of a PHP Setup: Binary, php.ini, Extensions, and PHP-FPM#

Before diving into the fix-it steps, let’s quickly look at the key parts of a typical PHP setup:

• PHP Binary – The main engine that runs your PHP scripts.
• php.ini File – The config file that controls things like error reporting, memory limits, and file uploads.
• PHP Extensions – Add-ons like MySQL drivers or image processing libraries.
• PHP-FPM (FastCGI Process Manager) – Manages PHP processes when working with a web server like Nginx or Apache.
• Web Server – Apache, Nginx, etc. It passes web requests to PHP and serves the results.

Understanding how these parts work together makes troubleshooting way easier. Now, let’s fix things up!

1. PHP Command Not Found? How to Install PHP on Ubuntu, CentOS, or macOS#

Tried running php -v and got a "command not found" error? That means PHP isn’t installed—or your system doesn’t know where to find it.

Install PHP#

On Ubuntu:

On CentOS:

On macOS (with Homebrew):

Verify Installation#

Run:

If that doesn’t work, check if PHP is in your system’s $PATH. If not, you’ll need to add it.

Full PHP install guide on phoenixnap

2.Missing php.ini? How to Locate or Create Your PHP Configuration File#

You’ve installed PHP, but it’s not picking up your php.ini configuration file? You might see something like:

Find or Create php.ini#

Common locations:

• /etc/php.ini
• /usr/local/lib/php.ini
• Bitnami stacks: /opt/bitnami/php/etc/php.ini

If missing, copy a sample config:

Then restart PHP or PHP-FPM to apply the changes.

Understanding php.ini

3. How to Set the PHPRC Variable to Load Your Custom php.ini File#

Still no luck loading the config? Set the PHPRC environment variable to explicitly tell PHP where your config file lives:

To make it stick, add it to your shell config (e.g. ~/.bashrc or ~/.zshrc):

Learn more: PHP Environment Variables Explained

4. PHP-FPM Crashed? Restart PHP FastCGI Process to Fix 502 Errors#

Getting a 502 Bad Gateway? That usually means PHP-FPM is down.

Restart PHP-FPM#

On Ubuntu/Debian:

On CentOS/RHEL:

Bitnami stack:

Check if it's running:

If not, check the logs (see below).

5. php.ini-development vs php.ini-production: Which Should You Use?#

PHP offers two default config templates:

• php.ini-development – More error messages, ideal for dev work.
• php.ini-production – Safer settings, ideal for live sites.

Pick the one that fits your needs, and copy it to the right spot:

More details: PHP Runtime Configuration

6. Still Stuck? Use PHP and PHP-FPM Logs to Debug Errors#

Logs are your best friends when troubleshooting.

PHP error log:

PHP-FPM error log:

These will give you insight into config issues, missing extensions, and more.

Common PHP Errors & Fixes

Conclusion: How to Get PHP Running Smoothly Across Different Environments#

Getting PHP working can be frustrating at first, but once you understand the pieces—PHP binary, php.ini, extensions, PHP-FPM, and the web server—it’s much easier to fix issues when they pop up.

To recap:

• Install PHP
• Make sure php.ini is where PHP expects
• Set PHPRC if needed
• Restart PHP-FPM if you're using Nginx/Apache
• Check your logs

Once everything is running smoothly, your PHP-powered site or app will be good to go.

Simplify JSP Deployment – Powered by Nife.
Build, Deploy & Scale Apps Faster with Nife.

If you've used PDF.js in JavaScript projects, you might have noticed the pdfjs-dist package provides files in ES6 module format (.mjs). But what if your project needs UMD-compatible .js files instead?
In this guide, I'll show you how to automatically transpile PDF.js from .mjs to UMD using Babel—no manual conversion required.

Why Use UMD Instead of ES6 Modules for PDF.js Integration?#

Before we dive in, let’s clarify the difference:

ES6 Modules (.mjs)

• Modern JavaScript standard
• Works natively in newer browsers and Node.js
• Uses import/export syntax

UMD (.js)

• Works in older browsers, Node.js, and AMD loaders
• Better for legacy projects or bundlers that don’t support ES6

If your environment doesn’t support ES6 modules, UMD is the way to go.

See how module formats differ →

How to Use Babel to Transpile PDF.js from ES6 Modules to UMD Format#

Instead of searching for pre-built UMD files (which may not exist), we’ll use Babel to convert them automatically.

Step 1:Install Babel and Required Plugins for UMD Conversion#

First, install these globally (or locally in your project):

• @babel/cli → Runs Babel from the command line
• @babel/preset-env → Converts modern JS to compatible code
• @babel/plugin-transform-modules-umd → Converts modules to UMD format

For more on Babel configurations, check out the official Babel docs.

Step 2: Create a Shell Script to Transpile PDF.js from .mjs to UMD#

Save this as transpile_pdfjs.sh:

Merge multiple PDFs into a single file effortlessly with our Free PDF Merger and Split large PDFs into smaller, manageable documents using our Free PDF Splitter.

Step 3:Run Your Babel Transpilation Script for PDF.js#

1. Make it executable:

   chmod +x transpile_pdfjs.sh

   Copy

2. Execute it:

   ./transpile_pdfjs.sh

   Copy

What the PDF.js Babel Transpilation Script Actually Does#

✔ Checks for Babel → Ensures the tool is installed.
✔ Creates a umd folder → Stores the converted .js files.
✔ Transpiles .mjs → UMD → Uses Babel to convert module formats.
✔ Skips minified files → Avoids re-processing .min.mjs.

Want to automate your JS build process further? Check out this BrowserStack.

Final Thoughts: Make PDF.js Compatible with All Browsers Using UMD Format#

Now you can use PDF.js in any environment, even if it doesn’t support ES6 modules!

🔹 No manual conversion → Fully automated.
🔹 Works with the latest pdfjs-dist → Always up-to-date.
🔹 Reusable script → Run it anytime you update PDF.js.

And if you want to bundle your PDF.js output, Rollup’s guide to output formats is a great next read.
Next time you need UMD-compatible PDF.js, just run this script and you’re done!
Simplify the deployment of your Node.js applications Check out this nife.io.

If your WordPress site hosted on AWS Lightsail freezes at 33% when loading, don’t panic—this is a common issue, often caused by a misbehaving plugin. Since Lightsail runs WordPress in a managed environment, plugin conflicts or performance bottlenecks can sometimes cause this problem.

In this guide, I’ll walk you through troubleshooting steps to identify and fix the problematic plugin so your site loads properly again.

Why WordPress Freezes at 33% on AWS Lightsail (Common Causes Explained)#

When your site hangs at 33%, it usually means WordPress is waiting for a response from a slow or failing process—often a plugin. This could happen because:

• A plugin is conflicting with another plugin or theme
• An outdated plugin is incompatible with your WordPress or PHP version
• A resource-heavy plugin (like backup or SEO tools) is slowing things down
• A buggy plugin is causing errors that prevent the page from loading

Since AWS Lightsail doesn’t provide direct error logs in the dashboard, we’ll need to manually check and disable plugins to find the culprit.

Step-by-Step Guide to Fix WordPress Stuck at 33% Using SSH#

Step 1: Log Into AWS Lightsail via SSH to Access WordPress#

Since you can’t access the WordPress admin dashboard (because the site is stuck), you’ll need to log in to your Lightsail instance via SSH:

1. Go to the AWS Lightsail console.
2. Click on your WordPress instance.
3. Under "Connect", click "Connect using SSH" (or use your own SSH client with the provided key).

Once connected, navigate to the plugins folder:

More on SSH access in Lightsail

Step 2: Disable All WordPress Plugins via SSH for Troubleshooting#

To check if a plugin is causing the issue, we’ll disable all of them at once by renaming the plugins folder:

This adds _disabled to each plugin’s folder name, making WordPress ignore them.

Step 3: Test the Site After Disabling Plugins#

After disabling plugins, refresh your WordPress site. If it loads normally, the problem is definitely plugin-related.

Step 4: Re-enable WordPress Plugins Individually to Identify the Problematic One#

Now, we’ll re-enable plugins one at a time to find the troublemaker.

For example, to re-enable "Yoast SEO", run:

After enabling each plugin, refresh your site. If it freezes again, the last plugin you enabled is likely the issue.

Step 5: Clear WordPress Cache and Restart Apache in Bitnami Stack#

Sometimes, cached data can interfere. Clear the cache and restart your web server:

Bitnami restart commands

How to clear WordPress cache properly

This ensures changes take effect.

Step 6: Update, Replace, or Remove the Faulty WordPress Plugin#

Once you’ve found the faulty plugin, you have a few options:

✔ Update it – Check if a newer version is available.
✔ Find an alternative – Some plugins have better alternatives.
✔ Contact support – If it’s a premium plugin, reach out to the developer.

Find plugin alternatives on WordPress.org

Best practices for evaluating WordPress plugins

Final Thoughts: Restore Full WordPress Functionality on AWS Lightsail#

A WordPress site freezing at 33% is frustrating, but the fix is usually straightforward—a misbehaving plugin. By disabling plugins via SSH and re-enabling them one by one, you can quickly identify the culprit.

Since AWS Lightsail doesn’t provide detailed debugging tools, this manual method is the most reliable way to troubleshoot. Once you find the problematic plugin, updating, replacing, or removing it should get your site back to normal.

Ask questions or share your experience on the Bitnami Community Forum

To deploy a static site or frontend framework (e.g., React, Vue, Angular), refer to the Nife Build File Deployment guide for configuring and uploading your build assets.

Check out our solutions on nife.io