Troubleshooting Guide

Troubleshooting Guide

Having issues with MarkdownBlog? This comprehensive troubleshooting guide covers common problems and solutions to get you back to creating content quickly.

Common Login Issues

Can't Sign In to Your Account

Problem: Login fails with correct credentials

Solutions: 1. Check Email and Password - Verify email spelling (common typos: gmail.com vs gmial.com) - Ensure Caps Lock is not enabled - Check for extra spaces before/after credentials

2. Clear Browser Data

   Chrome: Settings > Privacy > Clear Browsing Data
   Firefox: Settings > Privacy > Clear Data
   Safari: Preferences > Privacy > Clear All Website Data
   ``

3. Try Incognito/Private Mode - Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) - Firefox: Ctrl+Shift+P (Windows) or Cmd+Shift+P (Mac) - Safari: Cmd+Shift+N

4. Reset Password - Click "Forgot Password" on login page - Check email (including spam folder) - Follow reset instructions

Still Not Working? - Try a different browser - Disable browser extensions temporarily - Contact support with your account email

Google OAuth Issues

Problem: "Continue with Google" not working

Solutions: 1. Check Browser Settings - Allow popups for markdownblog.com - Enable third-party cookies - Disable strict privacy settings temporarily

2. Google Account Issues - Ensure you're signed into the correct Google account - Try signing out of all Google accounts and back in - Clear Google cookies specifically

3. Browser Compatibility - Use Chrome, Firefox, Safari, or Edge - Update browser to latest version - Disable ad blockers temporarily

Error Messages: - "OAuth error": Check popup blockers and try again - "Invalid redirect": Clear browser cache and retry - "Access denied": Ensure you're authorizing the correct permissions

Editor Problems

Editor Not Loading or Responding

Problem: Editor appears blank or doesn't respond to typing

Solutions: 1. Browser Compatibility - Use supported browsers (Chrome 70+, Firefox 65+, Safari 12+, Edge 79+) - Update browser to latest version - Disable browser extensions

2. JavaScript Issues - Ensure JavaScript is enabled - Clear browser cache and reload - Check browser console for error messages

3. Network Connection - Check internet connection stability - Try refreshing the page - Switch to a different network if possible

Advanced Troubleshooting:

javascript // Open browser console (F12) and check for errors console.log("Editor debugging info");

Auto-Save Not Working

Problem: Changes aren't being saved automatically

Solutions: 1. Check Connection - Verify internet connection is stable - Look for "Connection lost" messages - Try manual save (Ctrl+S/Cmd+S)

2. Browser Settings - Disable strict privacy modes - Allow cookies for markdownblog.com - Check local storage permissions

3. Storage Space - Clear browser cache if it's full - Close unnecessary browser tabs - Restart browser if memory is low

Indicators of Auto-Save Issues: - No "Saved" indicator appearing - Warning messages about connection - Changes lost after page refresh

Preview Not Updating

Problem: Right pane doesn't show markdown changes

Solutions: 1. Refresh the Preview - Click anywhere in the preview pane - Scroll in the preview to trigger update - Refresh the entire page

2. Markdown Syntax Issues - Check for unclosed code blocks (`) - Verify heading syntax (space after #) - Look for malformed links or images

3. Browser Performance - Close other resource-intensive tabs - Disable unnecessary browser extensions - Try using fewer formatting elements

Common Syntax Issues:

markdown ❌ #Heading without space ✅ # Heading with space

`javascript (unclosed code block) ✅

code here

linklink `

Publishing and Blog Issues

Blog Not Showing Published Content

Problem: Posts appear published but don't show on blog

Solutions: 1. Check Blog Status - Go to Dashboard > Hosting - Verify blog is set to "Published" - Check if blog URL is accessible

2. Post Status Verification - Ensure posts are marked as "Published" not "Draft" - Check post creation date and time - Verify content is not empty

3. Cache Issues - Clear browser cache - Try accessing blog in incognito mode - Wait 5-10 minutes for changes to propagate

URL Troubleshooting: - Correct URL format: /u/yourusername - Check for typos in username - Ensure blog is actually published, not just posts

Custom Domain Not Working

Problem: Custom domain doesn't redirect to your blog

Solutions: 1. DNS Configuration (Growth/Pro plans only) ` CNAME record: www.yourdomain.com → markdownblog.com A record: yourdomain.com → [IP provided by support] `

2. Domain Setup Verification - Check DNS propagation (can take 24-48 hours) - Verify domain is added in MarkdownBlog settings - Ensure domain is pointing to correct servers

3. SSL Certificate Issues - Allow 1-2 hours for SSL certificate generation - Check if https:// works vs http:// - Contact support for certificate problems

DNS Tools for Verification: - dig yourdomain.com (command line) - nslookup yourdomain.com - Online DNS checkers

Template Not Applying

Problem: Blog appearance doesn't match selected template

Solutions: 1. Clear Cache - Hard refresh browser (Ctrl+F5/Cmd+Shift+R) - Clear browser cache completely - Try different browser

2. Template Settings - Go to Blog Settings > Template - Re-select template and save - Verify template change saved successfully

3. Content Compatibility - Ensure content works with selected template - Check for template-specific formatting requirements - Verify all required fields are filled

Content and Formatting Issues

Images Not Displaying

Problem: Images appear as broken links or don't load

Solutions: 1. Image URL Verification - Ensure image URLs are accessible publicly - Check for https:// protocol (required) - Verify image file extensions (.jpg, .png, .gif, .webp)

2. Image Hosting - Use reliable image hosting services - Avoid localhost or private network URLs - Ensure images allow external linking

3. Markdown Syntax `markdown ❌ !Alt text ✅ !Alt text ❌ ![](image.jpg) - relative path won't work ✅ !Alt text `

Recommended Image Hosts: - Imgur (free, reliable) - Cloudinary (advanced features) - GitHub (for open source projects) - Your own domain (Growth/Pro plans)

Code Blocks Not Highlighting

Problem: Code appears without syntax highlighting

Solutions: 1. Language Specification `markdown ❌ ` (no language specified) ✅ `javascript const greeting = "Hello, world!"; ``python print("Hello, world!") ` `

2. Supported Languages - JavaScript, Python, PHP, Java, C++, HTML, CSS - bash, shell, sql, json, yaml, markdown - For full list, see supported languages

3. Code Block Format - Use three backticks (`) not single () - Ensure closing backticks are on separate line - Don't mix tabs and spaces in code

Links Not Working

Problem: Links don't navigate correctly or show as plain text

Solutions: 1. Link Syntax ``markdown ❌ [Link text] (space before parentheses) ✅ Link textLink text - missing protocol ✅ Link text `

2. Internal Links `markdown ✅ Other PostHomepageExternal `

3. Link Validation - Test links in preview pane - Verify external URLs are accessible - Check for typos in URLs

Performance Issues

Slow Loading or Timeouts

Problem: Editor or blog loads slowly or times out

Solutions: 1. Network Optimization - Check internet connection speed - Try different network (mobile hotspot, different WiFi) - Disable VPN if using one

2. Browser Optimization - Close unnecessary tabs and applications - Clear browser cache and cookies - Disable resource-heavy extensions

3. Content Optimization - Reduce large image sizes - Minimize use of external embeds - Break very long posts into smaller sections

Performance Testing: - Test on different devices - Check during different times of day - Compare performance across browsers

High Memory Usage

Problem: Browser becomes slow or crashes when using editor

Solutions: 1. Browser Resource Management - Close unused tabs - Restart browser periodically - Use latest browser version

2. Content Management - Edit shorter posts when possible - Use "Save Draft" frequently - Break large documents into multiple posts

3. System Resources - Close unnecessary applications - Ensure adequate RAM available - Consider using a different device for large content

Account and Billing Issues

Plan Upgrade Problems

Problem: Payment completed but plan not upgraded

Solutions: 1. Wait for Processing - Allow 2-4 hours for manual activation - Check email for confirmation - Verify payment was successful

2. Payment Verification - Include your account email in payment notes - Send exact amount shown on upgrade page - Use payment references for tracking

3. Contact Support - Provide payment reference number - Include account email address - Attach payment confirmation if available

Usage Limit Concerns

Problem: Approaching or exceeding usage limits

Solutions: 1. Monitor Usage - Check dashboard for current usage - Review usage patterns and trends - Plan content creation accordingly

2. Optimize Usage - Archive or delete unnecessary posts - Optimize images to reduce page load impact - Focus on high-quality content over quantity

3. Plan Adjustment - Upgrade to higher plan if needed regularly - Consider usage patterns for plan selection - Take advantage of annual billing savings

Mobile App Issues

Mobile Browser Problems

Problem: Issues using MarkdownBlog on mobile devices

Solutions: 1. Browser Selection - Use Chrome, Firefox, or Safari mobile - Avoid outdated mobile browsers - Update browser to latest version

2. Mobile Optimization - Use landscape orientation for editing - Enable desktop mode for complex editing - Consider tablet for extensive writing

3. Touch Interface Issues - Tap precisely on buttons and links - Use long-press for context menus - Scroll gently to avoid accidental taps

Mobile-Specific Features: - Swipe gestures for navigation - Pinch-to-zoom for detailed editing - Voice-to-text for content input

Advanced Troubleshooting

Browser Console Debugging

Problem: Need detailed error information

Solutions: 1. Open Developer Tools - Chrome/Firefox: F12 or Ctrl+Shift+I - Safari: Cmd+Option+I - Edge: F12 or Ctrl+Shift+I

2. Check Console Tab - Look for red error messages - Note any warning messages - Take screenshots of errors

3. Network Tab Analysis - Check for failed requests - Verify API calls are completing - Look for slow-loading resources

Clearing Specific Data

Problem: Need to clear only MarkdownBlog data

Solutions: 1. Site-Specific Cache ` Chrome: Settings > Privacy > Site Settings > markdownblog.com Firefox: Address bar > Shield icon > Clear cookies and site data Safari: Preferences > Privacy > Website Data > Remove markdownblog.com ``

2. Local Storage - Open Developer Tools - Go to Application/Storage tab - Clear localStorage for markdownblog.com

3. Session Storage - Also in Developer Tools > Application - Clear sessionStorage entries - Refresh page after clearing

Getting Additional Help

When to Contact Support

Contact support if: - Solutions here don't resolve your issue - You're experiencing data loss - Payment or billing problems occur - Bug reports or feature requests - Account security concerns

Information to Include

When contacting support, provide: - Your account email address - Detailed description of the problem - Steps you've already tried - Browser and operating system information - Screenshots or error messages - Time when issue occurred

Support Response Times

Response Time Expectations: - Free Plan: Documentation and community forums - Starter Plan: 48-72 hours via email - Growth Plan: 24-48 hours via email - Pro Plan: 12-24 hours via email, priority support

Community Resources

Additional Help: - Community Forums - User discussions - FAQ - Frequently asked questions - Video Tutorials - Visual guides - Best Practices - User tips and tricks

Preventive Measures

Avoid Issues by: - Keeping browsers updated - Regularly clearing cache - Monitoring usage limits - Backing up important content - Following best practices guides

---

Still need help? Contact our support team with detailed information about your issue, and we'll help you resolve it quickly.

Most issues can be resolved with the solutions above. For persistent problems or account-specific issues, our support team is here to help.